feat: fromJson? derivations now say where a parsing error occurred #1656
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consider the following structures
Previously, the expression in
#eval
would return an error"String expected"
. However often these parsing errors can occur in very deeply nested structures, making it hard to discover where exactly a string was inspected.This PR causes the
fromJson?
method to prepend the field where the failure occurred if parsing fails. So now the above example will yield"Test2.jam: Test1.hello: String expected"
, making it clear that the badly formed sub-json was injam.hello
.