-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify handling of --all-or-nothing
and --no-all-or-nothing
options
#1456
Conversation
Merge up done, please address the conflicts |
@greg0ire I'll be away for the weekend, but I'll push the rebase around Monday. |
da41dab
to
d9764d0
Compare
@greg0ire rebased onto |
We ignore it, since breaking changes (here, removing a class) are OK during a major upgrade. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please document the breaking changes in UPGRADE.md
d9764d0
to
51d59dd
Compare
@greg0ire I pushed a new entry in the |
Thanks @agustingomes ! |
Summary
Allowing passing values to options for
--all-or-nothing
option is now removed, which allows the configuration of the negatable option--no-all-or-nothing
, whihc in its turn allows to remove the added option in 3.8.1.The outcome is a much simpler logic to override the configuration of
all_or_nothing
via the CLI command.