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

Already on GitHub? Sign in to your account

Better JSON parse errors #141

Closed
lassewesth opened this Issue Nov 12, 2012 · 1 comment

Comments

Projects
None yet
3 participants
Owner

lassewesth commented Nov 12, 2012

@jakewins: 'When an incorrect JSON string is sent to the server, I get long complex stack traces. I'd rather like getting something that points out where the parse error occurred, much like what Cypher does.

Eg:

Parse error on line 0, row X:
{"some":"jeon}
             ^-- Dat ain't cool, man.

'

Owner

lassewesth commented Nov 12, 2012


values:

@davidegrohmann davidegrohmann removed the server label Oct 22, 2015

@jakewins jakewins closed this Dec 5, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment