Reorder DisplayName content blocks per review feedback #36445
Closed
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
Co-authored-by: ilonatommy <[email protected]>
Copilot
AI
changed the title
[WIP] Revise content order in Forms on Blazor DisplayName PR
Reorder DisplayName content blocks per review feedback
Dec 5, 2025
ilonatommy
reviewed
Dec 5, 2025
Member
ilonatommy
left a comment
ilonatommy
left a comment
There was a problem hiding this comment.
@copilot, I numbered the order of lines. Update your PR.
Co-authored-by: ilonatommy <[email protected]>
Contributor
Author
ilonatommy
approved these changes
Dec 5, 2025
Member
|
Useless, we cannot merge this. |
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.
Reordered content in
aspnetcore/blazor/forms/input-components.mdto improve logical flow based on review feedback on #36438.Changes
DisplayNamecomponent introduction[DisplayName]attribute example[Display]attribute introduction and exampleDisplayNamecomponent usage example[DisplayName]attributeThe final order places the
[DisplayName]attribute example immediately after the component introduction, followed by the[Display]attribute details, the comparison summary, and finally the component usage example, creating a more logical progression from simple to complex usage patterns.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews