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

Deserialization errors are near-useless for complicated objects #98

Open
vriesk opened this issue Dec 7, 2023 · 0 comments
Open

Deserialization errors are near-useless for complicated objects #98

vriesk opened this issue Dec 7, 2023 · 0 comments

Comments

@vriesk
Copy link

vriesk commented Dec 7, 2023

When deserializing a complex object with multiple levels of nested sub-structures, the errors encountered upon deserialization are near useless, because they completely lack context.

The internal ErrorImpl can tell me what kind of issue was encountered, but not where. When trying to debug a large structure, this requires spending a lot of time staring on it and trying to figure out what could have possibly got mismatched.

Would there be some hope for providing error context during deserialization? Serialization is much less of a concern here, because it is rather unlikely to be triggered by wrong external input.

Note: it's not just serde_dynamo that suffers from this, and maybe this must be addressed on serde level, unsure here.

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

No branches or pull requests

1 participant