Acceptable types is very strict 0.23.2 #2538
-
|
The change to accepted argument types in version 0.23.2 issue #2523 broke my code. In my case, it's a datetime.date that isn't being cast to a string, and date strings are allowed in OpenAPI so this list of accepted types (str, int, float, bool, None) seems too strict to me. This change will also break things that are int-like or float-like (say numpy types like np.int32) rather than pure-python numbers, even though it's perfectly safe to case these to strings. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Thanks for the note! I think more discussion here is merited. I think this is further encouragement for reverting the change and including it in a future release. See #2523 (comment) and #2539 |
Beta Was this translation helpful? Give feedback.
Thanks for the note! I think more discussion here is merited.
I think this is further encouragement for reverting the change and including it in a future release. See #2523 (comment) and #2539