fix(deps): update dependency react-redux to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
react-redux	dependencies	major	^5.0.7 -> ^6.0.0	source

---

Release Notes

reduxjs/react-redux

v6.0.1

Compare Source

This is a minor release with support for react-hot-loader and a few small bug fixes for edge cases.

While you're here, please stop by #​1177 to see our roadmap for the next versions of React Redux. We are aware that performance is not so hot in 6.0. Short version: We put too much traffic on React's context API, which isn't really designed for high levels of reads and writes. We're looking to reduce that load and get performance back on track in a minor release, so there won't be backwards compatibility concerns. We have a new extensive benchmark suite to keep us on track and ensure we're not regressing on speed in the future.

And yes, we know about Hooks. Check out #​1179.

Changes

• Fix for circular component object structures, such as Emotion styled components. (#​1122 by @​Andarist)
• Minor optimization: remove conditional (#​1131 by @​ericanderson)
• Ensure that component context prop really contains a React context (#​1134 by @​casdevs)
• react-hot-loader compatibility (#​1168/#​1137 by @​theKashey)
• Upgrade to react-is v16.7.0 (#​1174 by @​nobezawa)

v6.0.0

Compare Source

🎉 This is our first big release supporting the new Context API added in React 16.4!

As such, we now require React 16.4 or higher. Make sure to update your version when updating to this release.

This work has been mostly lead by @​cellog and @​markerikson, with special guest appearances by yours truly and a whole cast of helpful reviewers.

Note: If you'd like to know more about the changes in v6, and how the implementation has changed over time, see Mark's post Idiomatic Redux: The History and Implementation of React-Redux.

Breaking Changes

• The withRef option to connect has been replaced with forwardRef. If {forwardRef : true} has been passed to connect, adding a ref to the connected wrapper component will actually return the instance of the wrapped component.

• Passing store as a prop to a connected component is no longer supported. Instead, you may pass a custom context={MyContext} prop to both <Provider> and <ConnectedComponent>. You may also pass {context : MyContext} as an option to connect.

Behavior Changes

Any library that attempts to access the store instance out of legacy context will break, because we now put the store state into a <Context.Provider> instead. Examples of this include connected-react-router and react-redux-subspace. (The current implementation does also put the store itself into that same context. While accessing the store in context is not part of our public API, we will still try to make it possible for other libraries to access it, with the understanding that this could break at any time.)

Also, there is a behavior change around dispatching actions in constructors / componentWillMount. Previously, dispatching in a parent component's constructor would cause its children to immediately use the updated state as they mounted, because each component read from the store individually. In version 6, all components read the same current store state value from context, which means the tree will be consistent and not have "tearing". This is an improvement overall, but there may be applications that relied on the existing behavior.

Changes

• Use React.createContext() (#​1000 by @​cellog)
• Use Prettier (#​1071 by @​NMinhNguyen)
• Only run isValidElementType in development builds (#​1069 by @​alexreardon)
• Treat null as a valid plain object prototype in isPlainObject() (#​1075 by @​rgrove)
• Ensure connectAdvanced only re-renders if derived props change (#​1079 by @​epeli and @​markerikson)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.

[kontrollanten]

reduxjs/react-redux#1161 (comment)

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 6.x releases. However, if you upgrade to 6.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.