doc(Comments): support auto generate attribute table component in extensions

[Copilot]

Issues

fixed #7574

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Mechanical refactor using Source Generator already implemented. Attribute data source changes from manual to generated; display logic unchanged.

Verification

• Manual (required)
• Automated

Server project builds with 0 errors/warnings. All 130+ components verified with correct Name mappings.

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[bb-auto]

Thanks for your PR, @Copilot. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (81903b6) to head (1323205).
⚠️ Report is 23 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #7524   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          748       749    +1     
  Lines        32998     32976   -22     
  Branches      4588      4580    -8     
=========================================
- Hits         32998     32976   -22     

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR migrates from manual AttributeTable Items="@GetAttributes()" declarations to using Source Generator with the Name parameter across 130+ component sample files. The migration eliminates approximately 9,000 lines of hand-maintained attribute definitions by leveraging automatic attribute extraction.

Changes:

• Replaced manual AttributeTable declarations with Source Generator-based Name parameter
• Removed 124 obsolete GetAttributes() methods from code-behind files
• Updated ComponentAttributeCacheService to support both BootstrapBlazor and extension assemblies
• Changed AttributeItem properties from non-nullable to nullable strings
• Cleaned up orphaned XML documentation comments
• Improved XML documentation consistency in IEditorItem and EditorItem interfaces

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
src/BootstrapBlazor/Components/EditorForm/IEditorItem.cs	Updated XML documentation for Chinese translations to be more idiomatic
src/BootstrapBlazor/Components/EditorForm/EditorItem.cs	Improved XML documentation and replaced inheritdoc references
src/BootstrapBlazor.Server/Services/ComponentAttributeCacheService.cs	Enhanced caching logic to support both core and extension assemblies
src/BootstrapBlazor.Server/Data/AttributeItem.cs	Changed properties to nullable to support dynamic generation
src/BootstrapBlazor.Server/Components/Samples/*.razor.cs	Removed orphaned XML comments and unused variables

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The Chinese documentation says "获得" (get) but the property has both getter and setter based on the interface definition. The documentation should say "获得/设置" (get/set) to match the English version which correctly says "Gets or sets".

[Copilot]

Line 73 hardcodes the namespace as "BootstrapBlazor.Components" but this assumes all types are in this namespace. The previous code used type.FullName ?? $"BootstrapBlazor.Components.{type.Name}" which was more flexible. For extension assemblies or types in different namespaces, this hardcoded approach could fail to find the correct XML documentation member name.

Suggested change

	var typeName = $"BootstrapBlazor.Components.{type.Name}";
	var typeName = type.FullName ?? $"BootstrapBlazor.Components.{type.Name}";

[Copilot]

The Version property now returns null when xmlDoc is null or when no version is found. Previously, the code had a fallback to "10.0.0" on line 62 of the old code. Removing this default could result in null Version values being displayed in the attribute table. This may be intentional if you want to distinguish between components with and without explicit version info, but it's a behavioral change that should be considered.

Suggested change

	Version = GetVersion(xmlDoc, property),
	Version = GetVersion(xmlDoc, property) ?? "10.0.0",

[Copilot]

The AttributeItem properties changed from non-nullable strings with default values to nullable strings. This is a breaking change if any code relies on these properties never being null. Consumers of AttributeItem may now need to handle null values, which could lead to NullReferenceExceptions if not properly handled in UI rendering code.

[Copilot]

The variable name 'v' is not descriptive. It's used to store the inheritdoc reference value. Consider renaming to something more meaningful like 'inheritdocRef' or 'cref' to improve code readability.

Suggested change

	var v = summaryElement.Element("inheritdoc")?.Attribute("cref")?.Value;
	return v != null ? FindSummaryElement(xmlDoc, v) : summaryElement;
	var inheritdocRef = summaryElement.Element("inheritdoc")?.Attribute("cref")?.Value;
	return inheritdocRef != null ? FindSummaryElement(xmlDoc, inheritdocRef) : summaryElement;

[Copilot]

The PropertyType property documentation says "获得/设置" (Gets or sets) but according to the IEditorItem interface (line 18), it's a get-only property. The documentation should say "获得" (Gets) to match the actual property definition in the interface.

Suggested change

	/// <para lang="zh">获得/设置 属性类型</para>
	/// <para lang="en">Gets or sets the property type</para>
	/// <para lang="zh">获得 属性类型</para>
	/// <para lang="en">Gets the property type</para>

[Copilot]

The Ignore property documentation says "是否忽略显示" (whether to ignore display) but the interface documentation says "是否忽略当前编辑项" (whether to ignore the current edit item). The descriptions are inconsistent between the interface and the implementation. Consider using the more complete description from the interface or using inheritdoc.

Suggested change

	/// <para lang="zh">获得/设置 是否忽略显示</para>
	/// <para lang="en">Gets or sets whether the field is ignored</para>
	/// <inheritdoc cref="IEditorItem.Ignore"/>