Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error message quality: parse vs iparse #1057

Open
marcosh opened this issue Aug 11, 2023 · 0 comments
Open

Error message quality: parse vs iparse #1057

marcosh opened this issue Aug 11, 2023 · 0 comments

Comments

@marcosh
Copy link

marcosh commented Aug 11, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant