Clarification on using the @ prefix
#34570
Merged
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.
Fixes #34564
Thanks, @nicholasyin! 🚀 ... Hopefully, this will clarify the points. Whether or not you prefix for nonliterals is up to the dev. Per management's decision, we'll stick with the current approach and only prefix when necessary. The text and example updates here should help with these points. I've included an example now where there's a nonliteral (a count in
Count) that doesn't receive a prefix (Count="count"), and there's new text to explain what's going on.This goes along with sample app updates on dotnet/blazor-samples#461.
You can see the new components for the examples here ...
Thanks again! ... and Happy New Year! 🕺💃🥳🍾
Internal previews