check if options passed to resave/all are supported by subcommands
#16148
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
…ed-options-are-supported
[ci skip]
brandonkelly
deleted the
feature/cms-1348-resaveall-to-check-if-provided-options-are-supported
branch
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.
Description
The
resave/allcommand now checks if the options it’s being run with (like--with-fields) are supported by each command it’s supposed to call. If not (and the command is run interactively), ask a user to confirm if they wish to proceed, and if so (or the command isn’t run interactively), run it for the actions that support all the options.Related issues
cms-1348