feat: add DialogHeader component and FormField.Required marker#55
Merged
Conversation
Radzen's DialogService.OpenAsync only takes a plain title string, so every form dialog in a consuming app fell short of the design's richer two-line header (title + subtitle, border-separated from the body). DialogHeader closes that gap as a titleContent RenderFragment; FormField.Required adds the matching visual asterisk for required fields.
This was referenced Jul 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Prompted by nerdventures-studio/customer-portal#53: comparing that app's live UI against its design mockup ("AppFoundation Screens") showed every form dialog falling short of the intended two-line header (title + subtitle, border-separated from the body) — a limitation of
DialogService.OpenAsync(string title, ...), which only accepts a plain string.DialogHeader— a small presentational component (Title + optional Subtitle, bottom-bordered via a new.ag-dialog-headerclass) to pass as thetitleContentRenderFragment overload ofOpenAsync. Radzen still renders its own close button/wrapper around it — this only replaces the title area's content.FormField.Required— new bool param, renders a red.ag-requiredasterisk after the label when set. Purely visual (pair withRadzenRequiredValidatorfor actual validation) — closes another gap from the same comparison (mockups mark required fields, the app didn't).DESIGN.md: new "Dialogs" recipe under §5,Requireddocumented under "Forms", both new classes added to the §6 reference table.README.md:DialogHeaderadded to the components list.1.2.1→1.3.0(new feature).Test plan
dotnet restore --locked-mode— no lock-file drift (no new package deps)dotnet build -c Release— 0 warnings, 0 errorsdotnet test— 152/152 passing (6 new:DialogHeaderTests, 2 newFormFieldTestscases)dotnet csharpier format .— clean