Skip to content

Allow to continue after parse error - #4522

Closed
nlohmann wants to merge 3 commits into
developfrom
issue3989
Closed

nlohmann wants to merge 3 commits into
developfrom
issue3989

Conversation

@nlohmann

Copy link
Copy Markdown
Owner

Address #3989

@coveralls

coveralls commented Nov 29, 2024 •

Copy link
Copy Markdown

Coverage Status

coverage: 99.633% (-0.02%) from 99.649%
when pulling cd1e38d on issue3989
into 1b9a9d1 on develop.

@github-actions github-actions Bot added the tests label Nov 30, 2024
@github-actions

Copy link
Copy Markdown

This pull request has been marked as stale because it has had no activity for 30 days. While we won’t close it automatically, we encourage you to update or comment if it is still relevant. Keeping pull requests active and up-to-date helps us review and merge changes more efficiently. Thank you for your contributions!

@github-actions github-actions Bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Jan 18, 2025
@nlohmann

Copy link
Copy Markdown
Owner Author

Superseded by #5601. Instead of continuing after an error with the parser in an inconsistent state, it repairs the input (inserting missing separators, closing containers, replacing unreadable values with null), so the SAX events stay balanced and every key gets a value. The binary readers stop, but complete the value read so far.

This comment was written by Claude Code.

@nlohmann nlohmann closed this Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

L state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The parser doesn't allow parse_error() to return true and continue parsing.

2 participants