Router.PreferExactMatches has this comment on it:
|
/// Important: all applications should explicitly set this to true. The option to set it to false |
|
/// (or leave unset, which defaults to false) is only provided for backward compatibility. |
|
/// In .NET 6, this option will be removed and the router will always prefer exact matches. |
As of now, though, the option is still available and still false by default. The net effect is the "LegacyRoute" support constructed here:
|
Routes = PreferExactMatches |
|
? RouteTableFactory.Create(assemblies) |
|
: LegacyRouteTableFactory.Create(assemblies); |
ends of referencing and preventing a bunch of APIs that could otherwise by trimmed by the linker from getting trimmed in a default Blazor wasm app.
cc: @eerhardt, @javiercn
Router.PreferExactMatches has this comment on it:
aspnetcore/src/Components/Components/src/Routing/Router.cs
Lines 85 to 87 in dfe625f
As of now, though, the option is still available and still false by default. The net effect is the "LegacyRoute" support constructed here:
aspnetcore/src/Components/Components/src/Routing/Router.cs
Lines 159 to 161 in dfe625f
ends of referencing and preventing a bunch of APIs that could otherwise by trimmed by the linker from getting trimmed in a default Blazor wasm app.
cc: @eerhardt, @javiercn