-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
String passed to field: List[str]
gets coerced in a very unexpected way
#202
Comments
field: List[str]
gets coerced very unexpectedly
field: List[str]
gets coerced very unexpectedlyfield: List[str]
gets coerced in a very unexpected way
I think this is fixed by #200, will be released soon. |
Great, thank you! |
@samuelcolvin I'm on
instead of validation error. |
Yes, looks like #200 only works if you use |
No problem. Thank you for developing this library :) |
Should be fixed by #225, would be very useful if you could check that out and confirm it does everything you need. |
WOW, thanks for so quick fix. So, I've pip installed from github at this particular commit and Thank you again :) |
Merged, I'll deploy this in a few days. |
Great, it will simplify my code :) |
Using Python 3.6.5 and pydantic==0.10.
String seems to be treated as an Iterable of (sub)strings (technically it's true in Python), which leads to very unexpected behavior, to say the least; I'd call it a bug, even.
I hope it could be changed in the future, but how can I deal with it in the current version of
pydantic
?The text was updated successfully, but these errors were encountered: