Invalid JSON map parsed as OK

[edsiper]

The following invalid JSON map is parsed without problems:

{"team":"test", "cpu":"10", {"log": "test"}}

I am using the strict mode but the problem persist. any suggestions are welcome:

cc: @zserge @lunatikub

[pt300]

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 {"foo":::::::::::::::::::::::::::::::"bar"} will be parsed as valid JSON. And I'm wondering whether I should help make a bit of a code overhaul to improve validation or just submit small patches when problems like that get reported.

[edsiper]

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

[edsiper]

FYI: we applied a fix into our top level project:

fluent/fluent-bit#621