Update next redux wrapper about devfaq HOT 9 CLOSED

I can do it, but before that we have to merge #54

from devfaq.

We also need to decide on the strategy – we could migrate to complete static generation, but do we want to? Do we prefer to keep on using SSR?

from devfaq.

I think current way of rendering is good for this project.

from devfaq.

There is a problem with the newest version of next-redux-wrapper. After update and required changes application has a problem with routing. It is related to HYDRATE action added in 6 version of lib. Here you have simple use example of newest lib. https://github.com/vercel/next.js/blob/canary/examples/with-redux-wrapper/store/store.js

from devfaq.

I did some research, and I guess you're right, there's no need to migrate away from getInitialProps

from devfaq.

If you wanna check how it works you can run app on my fork's branch issue-8-migrate-from-getinitialprops.
Here you can find required changes: develop...mczeplowski:issue-8-migrate-from-getinitialprops

from devfaq.

So 5th version of next redux wrapper is working with app with no changes. The newest version (6th) require some changes, but after them our app has breaking routing, so it will be a bigger task. You can check this running my branch.

from devfaq.

Sounds good! Create a PR and I'll refactor routing later. I don't remember why I even did it this way.

from devfaq.

Fixed in #85

from devfaq.