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
missing fields when calling JsonDecoder.decodeJson (".b.c.v2(missing)") vs JsonDecoder.fromJsonAST ("Missing fields: v2, v3")
invalid types when calling JsonDecoder.decodeJson (".b.c.v1(expected '\"' got '1')") vs JsonDecoder.fromJsonAST ("Not a string value").
The errors reported by 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".
I opened a PR with a test for this incosistency: #765.
The text was updated successfully, but these errors were encountered:
andreisilviudragnea
changed the title
Derived JsonDecoder decodeJson vs fromJsonAST error consistency
Derived JsonDecoder decodeJson vs fromJsonAST error inconsistency
Oct 24, 2022
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"
.I opened a PR with a test for this incosistency: #765.
The text was updated successfully, but these errors were encountered: