#283: allowMinorUpdates false should imply allowMajorUpdates false #745
+209
−345
Conversation
This file contains 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
andrzejj0
force-pushed
the
issue-283-false-minor-implies-false-major
branch
from
a6f90b9
to
0623e86
Compare
|
Please review @slawekjaranowski |
slawekjaranowski
approved these changes
Oct 12, 2022
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.
Implementing #283: allowMinorUpdates false should also imply allowMajorUpdates equal to false.
Likewise, allowIncrementalUpdates false implies allowMinorUpdates and allowMajorUpdates false.
Not enforced, but the values are assumed. I think the changes are also intuitive, i.e. what most users expect.
Documentation has been updated.