Open rwilson opened 6 years ago
This was a puzzling behavior that i also had to track down. My opinion is that by default the library should not silently pass along invalid JSON until the lazy sequence is ultimately realized down the line, likely outside of whatever try/catch block one has put in place to handle decoding errors. Opt-in laziness would be better.
Specifically, when the malformed JSON is in an array.
It's easily demonstrated in a repl:
The
JsonParseException
isn't thrown until the lazy sequence is realized, which may not be until subsequent middleware or an endpoint.Options could be:
Thoughts?