Start of help URLs that can be displayed without Markdown parsing #9332
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
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.
Nearly every task has a
helpMarkDownproperty that looks like this, and the surrounding Markdown isn't very useful:@vtbassmatt, are you okay with me adding
helpURlproperties for raw help URLs to the tasks? To date, the tasks only have them embedded in thehelpMarkDownproperty. They look pretty ugly when displayed in our logs unparsed. It would be nicer to have the raw URLs that UIs can render however they'd like.If you agree with this PR, then later I'd like to validate the URLs (some point to GitHub instead of our docs) and bump the tasks' patch version numbers.