is better error messages for json parsing errors o...
# serializationc
christophsturm
04/19/2022, 10:02 AMis better error messages for json parsing errors on the roadmap? it would be cool have a list of problems.
listOf(MissingField("surname"), WrongType("age", was=INT, expected=STRING))e
ephemient
04/19/2022, 2:59 PMc
christophsturm
04/19/2022, 4:07 PMI guess my main idea is to instead of throwing as soon as one error is detected all errors should be collected and then an exception with a list of errors thrown.
e
ephemient
04/19/2022, 4:12 PMthe way that decoders are being passed into serializers, there is no way to recover from an error in one object in order to continue and find errors in another
c
christophsturm
04/19/2022, 4:12 PMok so this cannot be done in the json lib alone and needs support in core?
e
ephemient
04/19/2022, 4:13 PMyeah, I believe this would need some real support in serialization-core
ephemient
04/19/2022, 4:14 PMwell, I can imagine some hacks possible if you're decoding from a JsonElement, but not streaming
c
christophsturm
04/19/2022, 4:16 PMthis is only for error handling so it does not need to be fast, i can even start the whole parsing from scratch
christophsturm
04/19/2022, 4:17 PMright now I’m parsing the exception message to get a list of missing fields, but that gives me only the fields of the first object that fails, and no path
e
ephemient
04/22/2022, 1:02 PMthinking about this more, there's no way to get all errors without changing how the generated serializers work
c
christophsturm
04/22/2022, 1:22 PMCan you give an example?
6 Views