Fixes issue where --local flag would cause extensions commands to error out #4584
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
bkendall
requested changes
May 24, 2022
| @@ -34,6 +34,7 @@ marked.setOptions({ | |||
| export default new Command("ext:configure <extensionInstanceId>") | |||
| .description("configure an existing extension instance") | |||
| .withForce() | |||
| .option("--local", "deprecated") | |||
There was a problem hiding this comment.
Strongly, strongly consider printing a warning if --local is included. IIRC, you should be able to check options.local.
bkendall
approved these changes
May 24, 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.
Description
ext:*commands should not error out when run with --local, even though it was deprecated (fixes #4577)Scenarios Tested
Now with a warning message
