Add regression test for -no-
handling
#1304
Merged
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.
I had already fixed
-no-
in middle of option name and only looking for--no-
at start, but it got reported as a bug in #1301 before released. Adding a regression test since it got reported.ChangeLog
Fixed
-no-
in the middle of the option flag should not be treated as negatable. BUG: defining an option which includesno-
makes the option true by default #1301