Skip to content

Conversation

@abhisheks-gh
Copy link

This PR enforces strict JSON parsing for the null, true, and false keywords.

It fixes cases where the parser would accept invalid literals such as "nope",
"t123", or "fxxxx" by reading the first token and blindly skipping the remaining
bytes using skipFixedBytes().

The change updates readNull() and readBoolean() to validate exact keyword bytes
and fixes their usage across switch cases to avoid partial or incorrect matches.

@abhisheks-gh
Copy link
Author

Hi @svobol13 , could you please review this MR? It's a fix for issue #357.
Thanks.

@abhisheks-gh
Copy link
Author

abhisheks-gh commented Jan 3, 2026

Hey @taowen / @elifarley / @based2 / @plokhotnyuk, can someone review and approve my MR? Thanks in advance.

@abhisheks-gh
Copy link
Author

Hi @plokhotnyuk / @taowen / @based2 / @elifarley, following up on my MR which is on back of issue #357 . Could you please check and approve the MR?

thanks.

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

Successfully merging this pull request may close these issues.

1 participant