-
Notifications
You must be signed in to change notification settings - Fork 642
Redux-simple-router and React-Router replaceState interactions #69
Comments
This should be solved in master. There's been quite a few commits lately, so hopefully we'll see a new version soon. Btw, while waiting for a new release I depend on master instead of
|
Thanks I will try with master so! |
When I update my package.json like that, webpack starts to fail:
When I look at the package.json in node_modules/redux-simple-router I see |
Ah, my bad, I totally forgot it must be built :/ Sorry. You can fix this with:
So not exactly very nice, but it helps if you want to test it. @jlongster I think it's about time with a new release. Lots of new stuff in master right now (and I really should stop telling people to use master — it's not a very good recommendation :/) |
Thanks for responding, @kjbekkelund. Count me among those eager for a new release. When I build in-place per you instructions, I end up with a file at |
Sorry, I figured out that |
I spoke too soon, that didn't fix it. |
It was the missing |
Why does it need to be built? Does installing from a github repo not run the post-install hooks? |
Agreed. I really wanted to fix the devtools issue, and there were a few coding style tweaks I was going to do. I personally haven't been update to play with master yet. I can work on it in the next day or two. I really wanted to to at least look at the devtools issue. |
@jlongster I think it's because the build is setup to occur during the |
Ah right. I wonder if there's a way to get it working from a straight git install. |
Can you try master? I'm going to close this this week unless you can reproduce the issue. |
Closed this, let us know if you still have problems |
Sorry for the late reply, anyway 1.0 fixed my problem, thanks for the fix! |
Hello! I need to implement authentication mechanics to my application and so instead of starting from scratch I've used React-Router auth-flow example as example.
I'm facing a strange problem: from the
Login
component (roughly the same as the example above) I should be able to redirect to the previous visited route if auth is successfull:This path should be stored inside the location state object by the
onEnter
hook on a protected route:If I use this logic with
redux-simple-route
, inside theLogin
component the propsthis.location.state
isnull
, while, if disabled, contains the right nextPathname property.I think I've narrowed down the problem to these lines of
redux-simple-router
(68-71):It pushes the route to history (which it should be not necessary) and doesn't pass the state in the process.
A simple fix would be setting
changeId
in the initial state to0
but I don't know if it may cause other things to stop working...The text was updated successfully, but these errors were encountered: