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
I think this would provide a great deal of flexibility and open the way for users who want to use react-router (or any other routing library for that matter) using a minimal invasive change.
I'd be happy to discuss this further and also eventually provide a PR for this. Let me know what you think.
The text was updated successfully, but these errors were encountered:
There is a way where we can create the rootRoute object on Application Context and let each modules to assign their own route to the rootRoute, similar to FlowRouter.
I have a proposition on how mantra could support react-router (as discussed here) while maintaining modularity and not changing the mantra API at all.
We can use the "huge apps" pattern to do the route setup inside the mantra modules (routes.jsx as it is now).
The only thing we'd need to do is return the resulting route configuration here like this:
Or, if you plan to use to return something else from
init()
in the future:Then one could use the react route objects to build up the react-router root like this:
I think this would provide a great deal of flexibility and open the way for users who want to use react-router (or any other routing library for that matter) using a minimal invasive change.
I'd be happy to discuss this further and also eventually provide a PR for this. Let me know what you think.
The text was updated successfully, but these errors were encountered: