-
Notifications
You must be signed in to change notification settings - Fork 258
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
PydanticSerializationError missing validation error field name #1483
Comments
Seems like a reasonable request to me, I think this just needs some refactoring. cc @sydney-runkle |
Indeed, a good first issue if anyone wants to pick this up. |
I can pick this one up and contribute, can you please assign me along with @crdsteixeira? We can pair. Thanks, |
I'm up for it 😃 |
Hi @sydney-runkle , can you please assign us the issue? 😊 |
Hey @joabreu / @crdsteixeira just checking in to see if you are still working on this? I am new to Rust and looking for a way to contribute while learning so just bouncing around looking for issues that seem doable. Also would be psyched to peer code something like this. Let me know! |
Hi @wevonosky, yes we are still working on this |
I am getting quite a few of these
Expected 'int' but got 'float' - serialized value may not be as expected
warnings in the log files. Is there a way to callout the specific field name?I looked at Rust's exception and error message, and I don't see any "add_variable_context" flag.
If not easily possible, would it be possible to add the field name that is triggering the warning to PydanticSerializationError please.
The object that is triggering the exception has large number of sub-objects and fields, so going through all the fields would be very time consuming.
The text was updated successfully, but these errors were encountered: