Error message quality: `parse` vs `iparse`
Open
- Dominant language
- Haskell
- Stars
- 1.3k
- Forks
- 336
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 4
Description
The usage of `parse` or `iparse` produce different error messages, since the former is excluding the information about the `JSONPath` of where the parse error happened.
This means that different functions (e.g. `fromJSON` and `decodeEither`) will produce error messages with different error quality.
I think it would be interesting to at least document which functions produce error messages which provide information on the error path and which ones do not
Contributor guide
Assessment
This issue has not been assessed yet.