-
Notifications
You must be signed in to change notification settings - Fork 25
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
integrate with react-router v4 #12
Comments
Are you planning support react-router v4? |
bump ... Are you planning support react-router v4? |
yeah, there is such plan but I had no time for that recently... I will try to take a look at this in August |
if it helps at all, i had it (or so i thought) implemented ... it just didn't get the "roles" from the route ... when i hard coded things, it hid and showed as expected ... thanks for the update. edit: the proposed solution is to change Doing that caused an undefined in AuthorizedComponent.componentWillMount() ... for my hard coded testing i did ... then I had to change and of course i updated the required fields this all works when typing the URL manually into the browser, but when accessing it via LINK then it still loads when it shouldn't. After adding RoleAwareComponent, it loaded null but still went to my endpoint. Is this the current behavior? |
any update on this? |
+1 need this. |
+1 |
2 similar comments
+1 |
+1 |
As the new version of react-router is completely rewriten, it would be nice to add support for this version of react-router. Or maybe it is completely unnecesary now?
The text was updated successfully, but these errors were encountered: