We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
want to let users more easily see where deserialise errors comes from.
Ideally you can add serde_path_to_error and swap out the deserializer calls with serde_path_to_error::deserialize(deserializer)
serde_path_to_error
serde_path_to_error::deserialize(deserializer)
e.g.:
# original let value: Type = serde_json::from_str(data)? # replacement let deserializer = &mut serde_json::Deserializer::from_str(data); let value: Type = serde_path_to_error::deserialize(deserializer)?
There are some uncertainties here though:
serde_yaml
The text was updated successfully, but these errors were encountered:
alternative; https://github.com/eopb/serde_json_path_to_error if it implements the various wrappers (as requested in its issues)
Sorry, something went wrong.
No branches or pull requests
want to let users more easily see where deserialise errors comes from.
Ideally you can add
serde_path_to_error
and swap out the deserializer calls withserde_path_to_error::deserialize(deserializer)
e.g.:
There are some uncertainties here though:
serde_yaml
? we need this to handle yaml tagsThe text was updated successfully, but these errors were encountered: