You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 onserde
level, unsure here.The text was updated successfully, but these errors were encountered: