{"action":"created","issue":{"url":"https://api.github.com/repos/acdlite/redux-router/issues/214","labels_url":"https://api.github.com/repos/acdlite/redux-router/issues/214/labels{/name}","comments_url":"https://api.github.com/repos/acdlite/redux-router/issues/214/comments","events_url":"https://api.github.com/repos/acdlite/redux-router/issues/214/events","html_url":"https://github.com/acdlite/redux-router/issues/214","id":121907773,"number":214,"title":"rerender on route change","user":{"login":"mmahalwy","id":3749095,"avatar_url":"https://avatars.githubusercontent.com/u/3749095?v=3","gravatar_id":"","url":"https://api.github.com/users/mmahalwy","html_url":"https://github.com/mmahalwy","followers_url":"https://api.github.com/users/mmahalwy/followers","following_url":"https://api.github.com/users/mmahalwy/following{/other_user}","gists_url":"https://api.github.com/users/mmahalwy/gists{/gist_id}","starred_url":"https://api.github.com/users/mmahalwy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmahalwy/subscriptions","organizations_url":"https://api.github.com/users/mmahalwy/orgs","repos_url":"https://api.github.com/users/mmahalwy/repos","events_url":"https://api.github.com/users/mmahalwy/events{/privacy}","received_events_url":"https://api.github.com/users/mmahalwy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-13T08:45:59Z","updated_at":"2015-12-19T00:30:58Z","closed_at":null,"body":"is it just me or the previous route's component rerenders right before a transition to the new one due to params changing and react-redux passing through props the new props to the old route.\r\n\r\nI found the only way to get around this is to implement my own `shouldComponentUpdate`. Any suggestions or anyone found same challenge?"},"comment":{"url":"https://api.github.com/repos/acdlite/redux-router/issues/comments/165926837","html_url":"https://github.com/acdlite/redux-router/issues/214#issuecomment-165926837","issue_url":"https://api.github.com/repos/acdlite/redux-router/issues/214","id":165926837,"user":{"login":"apapirovski","id":20809,"avatar_url":"https://avatars.githubusercontent.com/u/20809?v=3","gravatar_id":"","url":"https://api.github.com/users/apapirovski","html_url":"https://github.com/apapirovski","followers_url":"https://api.github.com/users/apapirovski/followers","following_url":"https://api.github.com/users/apapirovski/following{/other_user}","gists_url":"https://api.github.com/users/apapirovski/gists{/gist_id}","starred_url":"https://api.github.com/users/apapirovski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apapirovski/subscriptions","organizations_url":"https://api.github.com/users/apapirovski/orgs","repos_url":"https://api.github.com/users/apapirovski/repos","events_url":"https://api.github.com/users/apapirovski/events{/privacy}","received_events_url":"https://api.github.com/users/apapirovski/received_events","type":"User","site_admin":false},"created_at":"2015-12-19T00:30:58Z","updated_at":"2015-12-19T00:30:58Z","body":"@mmahalwy That is correct. `connect`-ed components will propagate state changes first before a render with the new component tree happens. Unfortunately, there's no good solution to it the way redux-router is implemented.\r\n\r\nTo be honest, as someone using this in production, I think for full compatibility with `redux`, there needs to be a router that's completely independent of `react-router` but dependent on `history`. Otherwise you have to architect your whole app (and its stores) to work around these type of incompatibilities."}}