BREAKING(yaml): rename StringifyOptions.noCompatMode
to StringifyOptions.compatMode
#5287
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.
What's changed
The
ParseOptions.noCompatMode
option has been renamed toParseOptions.compatMode
. As a result, the polarity of the option has been swapped. In other words,true
behavior has been changed tofalse
behavior, and visa-versa. This only affects users who currently useParseOptions.noCompatMode
.Motivation
This change makes the option far easier to understand by avoiding a negative-tensed name.
Migration guide
Use
ParseOptions.compatMode
instead ofParseOptions.noCompatMode
and swap the polarity of the option.Related
Towards #5124