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

Alternative JSON parsers? #19

Open
Eric24 opened this issue Oct 12, 2018 · 0 comments
Open

Alternative JSON parsers? #19

Eric24 opened this issue Oct 12, 2018 · 0 comments

Comments

@Eric24
Copy link

Eric24 commented Oct 12, 2018

I see in the code that parse is defined as JSON.parse, but that JSON.parse is explicitly used elsewhere. If parse were used everywhere, it would be simple (and very useful) to add "options" support for an alternative JSON parser (i.e. one that handles circular references without throwing an exception). The use or and choice of such a parser would be left completely to the user of jsonQ, by simply passing in a reference to the external parser, replacing the parse: JSON.parse.

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