Skip to content
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

Make PropertyMissingButRequired more informative #202

Closed
magnusart opened this issue Nov 25, 2024 · 2 comments · Fixed by #206
Closed

Make PropertyMissingButRequired more informative #202

magnusart opened this issue Nov 25, 2024 · 2 comments · Fixed by #206

Comments

@magnusart
Copy link

Hi

When using the library I've gotten the deserialization PropertyMissingButRequired error a few times. This is probably correct but I'd like to have some inkling that would inform me about exactly which property is missing and what type that property was expected to have had.

The error is thrown from the code line for below link. I have put a breakpoint in order to end up there whilst debugging. While I deduced some hints from that, it's time consuming to do that in a larger codebase.

{
Err(DeError::PropertyMissingButRequired)

@knutwalker
Copy link
Collaborator

Hi @magnusart, thanks for the report. I've opened #206, which adds the expected field/property name to the error message. Is that enough to make it more informative in your usecase?

@magnusart
Copy link
Author

I just ran into this issue today again. So happy that there is a fix pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants