Enhance the Options config example #34459
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
Collaborator
Author
|
Ok, now I'm happy with it. 😆 |
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.
Fixes #34458
Thanks @gregoryagu! 🚀 ... How about this? It includes getting rid of the "MY" naming. I've been dropping "MY"-named things around here for years, and here's yet another one 😩 to get rid of.
The reason that this wasn't fleshed out in the first place is simply that the Blazor doc set is an add-on doc set. All of this is covered by the cross-linked Options article in the main doc set. However, it is nice to show the Razor component piece, and it may as well add the other pieces to make it work.
There's an effort underway to make the main doc set's Fundamentals node articles emphasize Razor component/Blazor examples. That's on-going work.
Internal previews