Repository navigation
Reject incompatible RFC 8785 generation options - #1102
Merged
Merged
Conversation
byroot
reviewed
Oct 8, 2026
ydah
force-pushed
the
fix-rfc8785-incompatible-options
branch
from
October 8, 2026 08:59
ae2a5af to
5ebb52f
Compare
ydah
force-pushed
the
fix-rfc8785-incompatible-options
branch
from
October 8, 2026 09:03
5ebb52f to
e37760a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reject nonempty whitespace options and enabled
ascii_only,script_safe, orallow_nanwithArgumentErrorwhenrfc8785is enabled.Validate configuration and generation, including options changed through State setters.
JSON.dumpdefaultsallow_nanto false whenrfc8785is enabled.JSON::Fragmentremains supported for reusing canonicalized fragments. Its contents are inserted as is; callers must ensure they are canonical.Addresses the incompatible-options TODO in #1091.