Support experimental extensions in CLI - #2830
Merged
Merged
Conversation
Member
Author
|
@kevinthecheung can you check the copy please? |
joehan
approved these changes
Nov 18, 2020
kevinthecheung
approved these changes
Nov 20, 2020
Co-authored-by: Kevin Cheung <kevinthecheung@users.noreply.github.com>
Member
Author
|
@huangjeff5 Can you also take a look and see if this fits well with the backend? |
Contributor
Looks good to me, although the concept of varying "audiences" only exists on the official extensions currently. We plan to add an "audience" field to extensions stored on the backend in Q1 sometime, so that we can migrate official extensions to use the backend. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Allow the CLI to show a warning message when the user is installing an experimental extension.
Scenarios Tested