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
Update attribute routing coverage and README stats
Corrected the number of supported RouteConfig properties in ATTRIBUTE_ROUTING.md from 12 to 13 and updated the README to reflect 11 attribute types instead of 9 for attribute routes.
Copy file name to clipboardExpand all lines: ATTRIBUTE_ROUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -575,7 +575,7 @@ The following table shows which `RouteConfig` properties are supported via attri
575
575
|`ComponentLoader`| ❌ No | N/A | Requires async lambda - use programmatic config |
576
576
|`Children`| ❌ No | N/A | Complex hierarchies - use programmatic config |
577
577
578
-
**Coverage:** 11 out of 12`RouteConfig` properties are supported via attributes (92% coverage).
578
+
**Coverage:** 11 out of 13`RouteConfig` properties are supported via attributes (92% coverage).
579
579
580
580
The two unsupported properties (`ComponentLoader` and `Children`) require complex programmatic logic that cannot be expressed declaratively through attributes. For these scenarios, use traditional programmatic `RouteConfig` objects.
0 commit comments