Update inline descriptions for DartCode settings #2930
Merged
Conversation
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
DanTup
approved these changes
Nov 4, 2020
Member
DanTup
left a comment
There was a problem hiding this comment.
Thanks! This all looks good to me. I'd somehow missed markdownDescription and it'd always bugged me I couldn't format things better.
Member
|
Tests failures look like unrelated flakes; will investigate on master if red after landing this. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's election day and I can't focus on complicated tasks today, so I'm investing some time in tidy-up work instead.
This pull request attempts to clean up some of the settings descriptions for the extension:
markdownDescriptionwhere appropriate to add hyperlinks andcode fencesI've tested this locally by running in the extension development host to make sure the changes are presented correctly in
launch.jsonand the settings editor.