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
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:
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.
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.
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:
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
The text was updated successfully, but these errors were encountered: