We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
As we were testing the lib quite a lot came the question of compliance toward JSON specs.
We've found this very interesting paper https://seriot.ch/projects/parsing_json.html and in particular the JSONTestSuite repository that aim at assessing how compliant various JSON parsers can be with the spec.
When I ran the test suite for yieldable-json, several "should have failed, but succeeded" cases surfaced.
For example, but not only:
["x",,]
[ "x", ParseError: ...]
{}}
{}
I'm wondering if we can do something about it, even though looking at the code, it seems sometimes to be on purpose.
Thank you!
Attached is the full list of cases that should have failed, but succeeded.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
As we were testing the lib quite a lot came the question of compliance toward JSON specs.
We've found this very interesting paper https://seriot.ch/projects/parsing_json.html and in particular the JSONTestSuite repository that aim at assessing how compliant various JSON parsers can be with the spec.
When I ran the test suite for yieldable-json, several "should have failed, but succeeded" cases surfaced.
For example, but not only:
["x",,]
will result in an array with the ParseError within[ "x", ParseError: ...]
{}}
will result in{}
I'm wondering if we can do something about it, even though looking at the code, it seems sometimes to be on purpose.
Thank you!
Attached is the full list of cases that should have failed, but succeeded.
The text was updated successfully, but these errors were encountered: