Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A more complete Router #16004

Closed
galvesribeiro opened this issue May 16, 2018 · 2 comments
Closed

A more complete Router #16004

galvesribeiro opened this issue May 16, 2018 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components

Comments

@galvesribeiro
Copy link
Member

Hello Blazor folks.

We at BlazorExtensions were looking for an enhanced/more complete router for Blazor. We have ways to do it without touch the current Blazor router but we feel that it would be too much work to wrap Blazor navigation into a HoC that would be responsible to render the proper components there.

So, in order to avoid that undertaking, we would like to contribute to Blazor repo the router work.

The first question is: Are Blazor team members already working on enhance the Router to be close in features to other frameworks' routers like ReactJS and Angular? In case of yes, and it would be released relatively soon, then we can close the issue and wait for it.

Otherwise, here are the features we would like to add to the current router:

  1. Declarative Routing
  2. Complex/Nested routes
  3. State passing between routes
  4. Lazy/Decomposed/modular routing
  5. Guards
  6. Routing Abstractions (allow plugable external/custom routers)

Those are the initial foundation we thought about that should be in place to allow more complete routing in Blazor apps.

Looking forward to hear from you guys.

Thanks

@richbryant
Copy link

richbryant commented May 17, 2018

One request - the ability to handle in-page anchors. Sometimes you want to link to a point on the same page rather than load a new one. <a href="#myLinkPoint>is a handy construct, even in a menu/navbar.

Something which Angular and Aurelia pretty much ignored, incidentally.

@SteveSandersonMS
Copy link
Member

The enhancements we have in mind are tracked at #5489. If you have additional feature requests, please feel free to add them there.

In terms of timing, we don't expect to make any router changes in the next couple of months as we are focused on other areas. It's great to hear that you're looking into building something more sophisticated, so I'd suggest going ahead with that. If you learn things that you'd eventually like to feed back into the built-in router, we'd definitely appreciate your contribution! Thanks.

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/blazor Oct 27, 2019
@mkArtakMSFT mkArtakMSFT added the area-blazor Includes: Blazor, Razor Components label Oct 27, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

No branches or pull requests

4 participants