Add option to C++ JSON Parser/Serializer to allow customers to affirmatively disable legacy bug-compatibilty behaviors. #23027
Conversation
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
3317e75 to
a3a4dc4
Compare
…atively disable legacy bug-compatibilty behaviors. Right now this flag already exists inside the implementation but is not exposed to callers. Since this implementation has now been stable and used for an extended period with this behavior, we did not continue working on adhoc burning down these nonconformant behaviors piecemeal, so by offering the flag 'publicly' it will enable users who want a more conformant implementation to get it much faster. The default behavior is unchanged. PiperOrigin-RevId: 791836360
a3a4dc4 to
6ea1640
Compare
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.
Add option to C++ JSON Parser/Serializer to allow customers to affirmatively disable legacy bug-compatibilty behaviors.
Right now this flag already exists inside the implementation but is not exposed to callers. Since this implementation has now been stable and used for an extended period with this behavior, we did not continue working on adhoc burning down these nonconformant behaviors piecemeal, so by offering the flag 'publicly' it will enable users who want a more conformant implementation to get it much faster.
The default behavior is unchanged.