2.0.0 breaking changes?

@kirill-konshin this is a great library but we’re having issues upgrading to 2.0.0-beta.4 from 1.3.5. We are using Next 6.0.0. Can you kindly add documentation on the breaking changes?

[DonovanCharpin]

Hi @hrdymchl, I just did the migration from next 4.X -> next 6.0.0 and the next-redux-wrapper migration from 1.3.5 to 2.0.0-beta.4.

I think the main thing I had to do was to migrate my main Wrapper (hoc) to the _app.js, after that my code was cleaner and I started the migration.

• Move withRedux to the _app.js
• Use connect from react-redux for all my pages
• Use props.router instead of props.url because of nextjs this time

I just checked my commit and this is the only thing I changed. Check the readme, it gives also some code to reuse when doing the _app.js migration to integrate with the next-redux-wrapper.

I have still one thing I don’t know how to fix. The props from mapStateToProps are not sent to MyApp so maybe there is a breaking change with this. I don’t find in the doc where I can pass this :

//_app.js

const mapStateToProps = state => {
  return {
    translations: state.translations.entities,
    config: state.config.entities,
    theme: state.theme.entities
  };
};

export default withRedux(initStore, mapStateToProps)(MyApp);

[kirill-konshin]

I bet the problem is here: https://gist.github.com/simplynutty/c2daeb74acef6fdfe672c80d65d85c74#file-withgraphql-js-L40 bc this place is not wrapped with Provider.