[dev-v5] docs(tab): Clarify Header vs HeaderTemplate XML documentation on FluentTab#4765
Merged
vnbaaij merged 1 commit intomicrosoft:dev-v5from Apr 29, 2026
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Clarifies the XML documentation for FluentTab’s Header vs HeaderTemplate parameters to reduce confusion (especially for AI-assisted scaffolding) and encourage correct usage.
Changes:
- Expanded
Headerdocs to explicitly describe plain-text usage and link toHeaderTemplatefor rich content. - Expanded
HeaderTemplatedocs to explicitly describe rich markup usage and link back toHeader. - Added remarks noting the v4 parameter renames (
Label→Header,Header→HeaderTemplate).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
vnbaaij
approved these changes
Apr 29, 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
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.
Problem
AI agents (GitHub Copilot, etc.) consistently generate
Text="..."instead ofHeader="..."when scaffoldingFluentTabcomponents. This is because:Headersaid only"Gets or sets the label of the tab."— the word "label" leads models to look for aLabelproperty (the v4 name), and when that is absent they fall back toText, which is the convention used by other Blazor UI frameworks (Telerik, MudBlazor, …).Headernaturally evokes rich/template content rather than a plain string, reinforcing the confusion withHeaderTemplate.Change
Improved the XML doc summaries for both parameters on
FluentTab.razor.cs:Header(plain-text string)HeaderTemplate(rich RenderFragment)Why this matters for AI agents
These doc summaries are extracted at build time into
FluentUIComponentsDocumentation.jsonand served by the Fluent UI Blazor MCP server. Clearer descriptions with a concrete usage example (Header="My Tab") and an explicit cross-reference between the two properties give models the signal they need to pick the right one without hallucinatingText.Files changed
src/Core/Components/Tabs/FluentTab.razor.cs