Skip to content
This repository has been archived by the owner on Oct 26, 2018. It is now read-only.

Makes sure the state in the store matches the state in history when using SSR #445

Merged
merged 1 commit into from
Sep 22, 2016

Conversation

dlmr
Copy link
Contributor

@dlmr dlmr commented Aug 26, 2016

This solves some problems where they would be out of sync on the first render when using server side rendering. The location would be the same for both of them but the key would be different resulting in some strange behaviour.

The application will now always dispatch a LOCATION_CHANGE on initial render. This was already done when not using server side rendering, meaning that the behaviour is similar between using server side rendering and not.

I have tested this manually and it seems to work fine. I have unfortunately not enough time right now to add more tests.

I believe that this PR supersedes #412 and will probably address #444 and #429.

This solves some problems where they would be out of sync on the first render when using server side rendering. The location would be the same for both of them but the key would be different resulting in some strange behaviour.

The application will now always dispatch a LOCATION_CHANGE on initial render. This was already done when not using server side rendering, meaning that the behaviour is similar between using server side rendering and not.
@ptomasroos
Copy link

Any news?

@dlmr
Copy link
Contributor Author

dlmr commented Sep 14, 2016

I don't have time at the moment to write tests but I believe the implementation is solid. Help here is appreciated.

@unRob
Copy link

unRob commented Sep 22, 2016

@dlmr These changes work for our project too, enabling the transition from server to client without a hitch. I'd love to have this PR land soon, could you help me figure out what the approach to tests should be so I can contribute with some?

@timdorr
Copy link
Member

timdorr commented Sep 22, 2016

OK, let's do it!

@timdorr
Copy link
Member

timdorr commented Sep 22, 2016

Out in 4.0.6. Sorry it took so long!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants