-
Notifications
You must be signed in to change notification settings - Fork 57
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
Integrating with react-boilerplate #158
Comments
I was working on the same thing myself the other day. This isn't particularly helpful, but I think you can't stuff routes in app.js like that because React-Boilerplate handles routes in routes.js via a different mechanism. |
@focuswish Not sure what you mean. Could you elaborate on "different mechanism"? Also, did you get it to work? If so, what approach did you take? |
Anyone put it to work? |
@williamgranli @focuswish Does it work if you pull in #174? I did some trial runs with the boilerplate, and didn't run into any issues, but I don't know how complex your use cases are. The issue was that Thanks for reporting this and the info you provided! |
@Tweety-FER Not using stormpath in our project anymore, so I won't be able to answer your question reliably, but to my knowledge react-boilerplate's route-generator uses objects (not components). (See function createRoutes in react-boilerplate/app/routes.js). |
Has anyone managed to integrate react-stormpath with the react-boilerplate project? I'm running into problems since react-stormpath has it's own Router. (I'm guessing it's just an extended version of react-router).
To begin with I'm skipping the createRoutes function and just adding them manually in app.js. When I get it to work I'll try to add it to the createRoutes function.
This is what I've done so far:
in app.js:
This works fine as long as I keep "routes={rootRoute}" commented out and just add them manually. This, of course, disables the reducer and saga injections. If I try to add the rootRoute object as the routes property to Router, I get the following error:
So it seems that the Router from react-stormpath can't handle objects... any idea how to fix this? I've tried to wrap createFragment around the rootRoute object as the error suggests and mapping the child elements out to an array, without success.
Any idea what's going on here and how I could solve it?
The text was updated successfully, but these errors were encountered: