Derived JsonDecoder decodeJson vs fromJsonAST error inconsistency tests #765
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.
JsonDecoder
s have different errors for:JsonDecoder.decodeJson
(".b.c.v2(missing)"
) vsJsonDecoder.fromJsonAST
("Missing fields: v2, v3"
)JsonDecoder.decodeJson
(".b.c.v1(expected '\"' got '1')"
) vsJsonDecoder.fromJsonAST
("Not a string value"
).JsonDecoder.fromJsonAST
seem to be broken because the JSON path to the error is missing from the messages:"Missing fields: v2, v3"
,"Not a string value"
.Scala 3 derived decoders fail at runtime with
StackOverflowError
for now. This might be another bug.