Update react-redux to the latest version 🚀 #129
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.
Version 5.0.0 of react-redux just got published.
The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react-redux.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v5.0.0This release is brought to you by contributions from the following people: @jimbolla, @vhmth, @btd, @roncohen, @ynonp, and @appden. In addition, there were many non-code contributions in discussions on issues and testing the alpha, beta, and rc versions by many other folks (too many to list!). Thank you to everyone who made this a very positive, inclusive, well-critiqued, community-driven release!
TL;DR
connect()
connectAdvanced()
APIAPI Compatibility
Version 5.0 maintains API compatibility with v4.x but due to major internal changes and potential behavior differences across nearly all API surfaces, semver dictates a major version bump. Also, it's good marketing! 💰 Store state change notifications sent to components are now guaranteed to occur top-down, so if your code may behave differently if it relied on notifications happening out of order.
Internal Changes
Internally, the code for
connect
has been rewritten from the ground-up to be more modular, with the intention of greater maintainability and extensibility. This has also led to some new features and performance improvements.Performance improvements
Significant performance gains were achieved by avoiding extra calls to
setState()
andrender()
by ensuring the order of change notifications to occur top-down, matching React's natural flow. Performance tests and benchmarks are discussed in #416.Bugfixes
Some bugs/issues are resolved, related to performance loss and also impure components not re-rendering.
New features added to connect()
The behavior of
connect()
is now more customizable, by passing additional properties in theoptions
arg. These will be described in the API docs.New top level API: connectAdvanced()
The new implementation of
connect()
splits its behavior such that it is now a wrapper around a more-generalizedconnectAdvanced()
. ThisconnectAdvanced()
method can be called directly if you have extreme performance needs or want to craft an API different than that ofconnect()
. This will be described in the API docs.What's next?
We're looking at removing the
shouldComponentUpdate
optimization. Since this version is much more performant on its own, that isn't needed. This will fix long-standing problems with other libraries that use React'scontext
API. There are workarounds, but things should work without either library authors having to bend over backwards or React having to make API changes.We will accept bugfixes on the 4.x branch (the 3.x branch will be going away; but the tags to 3.x versions will remain!), but new features should be built against the
next
branch. We love PRs, so keep them coming!Changes since v5.0.0-rc.1
Commits
The new version differs by 112 commits (ahead by 112, behind by 4).
e23991f
5.0.0
f892ec0
5.0.0-rc.2
710cb85
Update yarn deps
2000ff5
Fixes #525 (cursor bug) by moving notify from setState callback to componentDidUpdate. (#557)
1e5e7c4
5.0.0-rc.1
7e7790d
Update all our deps.
f41df99
Adds react15CompatibilityMode setting (#540)
582b17f
Shows more helpful error when connect() is passed invalid args. (#554)
d5180b5
Error message changed in React 15.
9e9c725
Don't pass props to divs to avoid unknown props errors.
f0df2d9
Bump up to React 15. Add a yarn.lock (for 😎-ness)
217e98a
Fix error from clear() called during notify() (#517)
0050678
Supress eslint error "react/display-name" at intentional omission.
8c3ecee
5.0.0-beta.3
4e8b313
Revert "warn on duplicate props" (#511)
There are 112 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴