-
Notifications
You must be signed in to change notification settings - Fork 3
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
Initial cut of routes and controllers #5
Comments
RE: Routing, we should be pretty much covered by react-router. Basically, once we make the pages, they're pretty simple to hook up.There's some fancy stuff we can do with react-router if/when we need to, but for now the basic routing functionality should be fine. RE: Controllers, we may want to think about adding redux ( or some other flux implementation? ). We don't need it right now, but once we implement the login functionality, the app might get complex enough to warrant adding it. |
The UI will need to handle routing and history changes to provide a good UI experience for browser based users. This should be handled by some kind of routing and controller dispatch scheme. This task is to create the basic stubs we know we will need to get off the ground:
Depends on #3
The text was updated successfully, but these errors were encountered: