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

no_match should point to erroneous tuple #4

Open
kpy3 opened this issue May 16, 2013 · 0 comments
Open

no_match should point to erroneous tuple #4

kpy3 opened this issue May 16, 2013 · 0 comments

Comments

@kpy3
Copy link

kpy3 commented May 16, 2013

If one tries to encode large proplist, it is difficult to find property with error because jsonx always points to first tuple:
3> jsonx:encode([{<<"b">>, false},{<<"a">>, 999999999999999999999999999999999999999999999999999}]).
{no_match,{<<"b">>,false}}

Pointing to tuple with error makes error finding easier.

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