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
{{ message }}
This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
from what I can see, react-little-router exceeds with little applications. If I am building a larger application I want to organize my routes in a single routes file which includes the components routes are mapped to, or even break up a routes into multiple files.
using your library, I have this helper so I can use a single file for my routes
would you consider including something like this? Something where routes dont need to be defined in both a routes object and in each Fragment? It makes a react-router app much easier to reason about. If that same logic can be applied without react-router that would be awesome!
The text was updated successfully, but these errors were encountered:
tptee
changed the title
reorganize routes object
Decouple Fragment matching from predefined routes
Mar 23, 2017
Check out #189 – Fragment matching is decoupled from static routes. Even better, you can just ditch static routes altogether if you don't want/need them!
from what I can see,
react-little-router
exceeds with little applications. If I am building a larger application I want to organize my routes in a single routes file which includes the components routes are mapped to, or even break up a routes into multiple files.using your library, I have this helper so I can use a single file for my routes
would you consider including something like this? Something where routes dont need to be defined in both a routes object and in each Fragment? It makes a react-router app much easier to reason about. If that same logic can be applied without react-router that would be awesome!
The text was updated successfully, but these errors were encountered: