clarify effect of command enablement - #110423
Merged
Merged
Conversation
Member
Author
|
CI failure seems unrelated. |
Johannes Rieken (jrieken)
approved these changes
Nov 12, 2020
Johannes Rieken (jrieken)
left a comment
Contributor
There was a problem hiding this comment.
Merging but also tweaking the working a little afterwards. Thanks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Tweaks the wording for
enablement's description to be more clear on what will be affected. That property only affects the UI, which is not clear to extension developers from the current description.