[11.0 P1] Forms on BLazor support DisplayName attribute
#36438
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
guardrex
approved these changes
Dec 4, 2025
Collaborator
guardrex
left a comment
guardrex
left a comment
There was a problem hiding this comment.
Thanks @ilonatommy ... Approving with tiny NITs.
I'll take care of the release notes. I'll ping you on that PR when it goes up within the next few days.
| public DateTime ProductionDate { get; set; } | ||
| ``` | ||
|
|
||
| [`[DisplayName]` attribute](xref:System.ComponentModel.DisplayNameAttribute) is also supported: |
Collaborator
There was a problem hiding this comment.
Suggested change
| [`[DisplayName]` attribute](xref:System.ComponentModel.DisplayNameAttribute) is also supported: | |
| The [`[DisplayName]` attribute](xref:System.ComponentModel.DisplayNameAttribute) is also supported: |
| public DateTime ProductionDate { get; set; } | ||
| ``` | ||
|
|
||
| Between the two approaches, the `[Display]` attribute is recommended, which makes additional properties available. The `[Display]` attribute also enables assigning a resource type for localization. When both attributes are present, `[Display]` takes precedence over `[DisplayName]`. If neither attribute is present, the component falls back to the property name itself. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Between the two approaches, the `[Display]` attribute is recommended, which makes additional properties available. The `[Display]` attribute also enables assigning a resource type for localization. When both attributes are present, `[Display]` takes precedence over `[DisplayName]`. If neither attribute is present, the component falls back to the property name itself. | |
| Between the two approaches, the `[Display]` attribute is recommended, which makes additional properties available. The `[Display]` attribute also enables assigning a resource type for localization. When both attributes are present, `[Display]` takes precedence over `[DisplayName]`. If neither attribute is present, the component falls back to the property name. |
guardrex
reviewed
Dec 5, 2025
| :::moniker range=">= aspnetcore-11.0" | ||
|
|
||
| --> | ||
| The <xref:Microsoft.AspNetCore.Components.Forms.DisplayName%601> component can be used to display property names from metadata attributes. The [`[Display]` attribute](xref:System.ComponentModel.DataAnnotations.DisplayAttribute) on the model class property is supported: |
Collaborator
There was a problem hiding this comment.
One other little problem here: The first line refers to the DisplayName component, but the second refers to the [Display] attribute. The component isn't covered until the end of the added content. Should that line be moved down here?
... OR ...
Since the component is mentioned in the paragraph on Line 479, should the component example at the bottom be moved to the top of this added content?
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.
Doc changes proposal for dotnet/aspnetcore#64636.
Issue: dotnet/aspnetcore#49147
Internal previews