Consider aligning how the @page directive works in razor components with how it works in razor pages

[danroth27]

The fix for this is to align the behavior of the @page directive with the Razor Pages behaviour, with one addition. If your page is in the Pages folder then that segment will be ignored.

If you don't like this, and you want direct control, you can use @attribute [Route(....)]

[mrlife]

This makes a lot of sense, especially with razor components used within a razor pages web app.

[gingters]

In my opinion, for a Blazor SPA routing should not require attributes at all.
In fact, the actual component should neither need nor require to know if it is used as a page (aka has a route) or a component, or both.

Also, if you want to provide re-usable components and pages for multiple applications under different routes (i.e. in a component or functionality library), the attribute approach is extremely inflexible as you can only have one definition on the attribute, and you need to copy & paste code or unnecessarily derive a new component from the shared one to provide different routes.

It would be much better to have a configurable routing system which you set up in Startup.cs (i.e. like in Angular, where you can define what route ends up at what component).
There could be an configuration that (ideally optionally and not even by default) uses the @page and @route attributes, but usually for real-world applications you want to have explicit control about your application routing and not mix your routing logic into the components which should be as agnostic about their usage as possible.

[mrlife]

Default and optional route parameters would be useful.

[TanayParikh]

@danroth27 is this something we're still looking to pursue? If so, would this be a 7.0 planning candidate?

[danroth27]

I think it's worth trying to get to a consistent place with @page. Let's make this a 7.0 candidate.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.