You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(skills): Clarify DetailsView+BoundField full support
- Add complete DetailsView+BoundField example in bwfc-migration skill
- Add note confirming IColumnCollection implementation works
- Emphasize: do NOT replace with HTML tables
- Both migration skills now have clear guidance
Fixes misconception from Run 11 report that claimed partial support.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: .github/skills/webforms-migration/SKILL.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -443,6 +443,8 @@ Data controls require additional changes for data binding:
443
443
- BoundField, TemplateField, and other column types work inside `<Fields>` just like Web Forms
444
444
- Child components (BoundField, TemplateField) **inherit the type parameter** via Blazor's `[CascadingTypeParameter]` — no `ItemType` needed on each child
445
445
446
+
> **✅ FULL SUPPORT:** DetailsView **fully supports** BoundField columns via the `<Fields>` wrapper. BWFC's DetailsView implements `IColumnCollection<ItemType>` which allows BoundField and other column types to register correctly. Do NOT replace DetailsView with HTML tables — use the BWFC component.
> **⚠️ NOTE:** DetailsView **fully supports** BoundField. Do NOT replace with HTML tables. The library implements `IColumnCollection<ItemType>` which allows BoundField and other column types to register correctly inside `<Fields>`.
0 commit comments