-
Notifications
You must be signed in to change notification settings - Fork 779
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
Invalid JSON map parsed as OK #131
Comments
After thonking for a moment I already see quite a simple solution for a problem. The thing is that I also see quite a bit of other parsing related problems. For example |
on top of my current JSMN I have applied PR #119 which adds more strict checks, so I see that a solution needs to be on top of that one. JSMN is really great, it just need more strict checks |
This patch also fixes the problem we previously reported in the jsmn repo: zserge/jsmn#131 Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
FYI: we applied a fix into our top level project: |
This patch also fixes the problem we previously reported in the jsmn repo: zserge/jsmn#131 Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
The following invalid JSON map is parsed without problems:
I am using the strict mode but the problem persist. any suggestions are welcome:
cc: @zserge @lunatikub
The text was updated successfully, but these errors were encountered: