feat: implemented flag conflicts in deploy.ts
#6909
Merged
+27
−3
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.
Implemented feature from
commander
to preventmutually exclusive flags from being run in the same command.
🎉 Thanks for submitting a pull request! 🎉
Summary
Fixes #3978
Before the change to
commander
, the CLI usedoclif
for defining commands and specifying flags.oclif
allowed for mutually exclusive flags when running commands—for example, when runningdeploy
with--prod
, the user shouldn't also be able to use--prodIfUnlocked
. Initially,commander
did not allow for mutually exclusive flags, but later implemented support for it. This PR re-implements the feature as it existed prior to moving tocommander
. We identified the conflicting flags by pulling in a commit that is chronologically prior to the issue this PR addresses.For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)