This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Update react-redux to the latest version 🚀 #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Pull Request Test Coverage Report for Build 428
💛 - Coveralls |
Update to this version instead 🚀 Release Notes for v6.0.1This 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
CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
|
|
|
|
|
|
|
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The dependency react-redux was updated from
5.1.1to6.0.0.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Release Notes for v6.0.0
🎉 This is our first big release supporting the new Context API added in React 16.4! No more blocked updates!
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.
Breaking Changes
The
withRefoption toconnecthas been replaced withforwardRef. If{forwardRef : true}has been passed toconnect, adding a ref to the connected wrapper component will actually return the instance of the wrapped component. (Known issue: Redux Form currently relies onwithRef.)Passing
storeas a prop to a connected component is no longer supported. Instead, you may pass a customcontext={MyContext}prop to both<Provider>and<ConnectedComponent>. You may also pass{context : MyContext}as an option toconnect.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 includeconnected-react-routerandreact-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
nullas a valid plain object prototype inisPlainObject()(#1075 by @rgrove)Commits
The new version differs by 17 commits ahead by 17, behind by 3.
581ece46.0.09062722Upgrade a bunch of deps.7564f73Fix bad URL generationcf11a25Add new "Why use React-Redux?" page (#1097)ce17d0cUpdate Docusaurus and docs URLs (#1096)f0840f16.0.0-beta.36a2e878Forgot to rebuild the lockfile.dba598bAdd connectAdvanced() tests (#1079)1dc56caRe-enable "should throw if not in context" test8987de0Treatnullas a valid plain object prototype inisPlainObject()(#1075)59aaba5Relax React peer dep back to 16.47496b916.0.0-beta.11a92b56npm audit fix0c048f0Use Prettier (#1071)85fb553Use React.createContext() by @cellog (#1000)There are 17 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴