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.
This PR contains the following updates:
2.1.1
->4.0.1
By merging this PR, the issue #2 will be automatically resolved and closed:
Release Notes
facebook/flux (flux)
v4.0.1
Compare Source
fbemitter
dependency to 3.xv4.0.0
Compare Source
fbjs
dependency to ^3.xv3.1.3
Compare Source
v3.1.2
Compare Source
v3.1.1
Compare Source
v3.1.0
Compare Source
Dispatcher
: Methodsregister
andunregister
can once again be called inthe middle of a dispatch.
v3.0.0
Compare Source
FluxMapStore
: Removed. It added very little value overFluxReduceStore
.FluxContainer
: Subscriptions are setup in constructor rather thancomponentDidMount
FluxContainer
: Can create containers using stateless functional componentsFluxContainer
: Uses functional version ofsetState
FluxMixin
: Subscriptions are setup incomponentWillMount
rather thancomponentDidMount
Dispatcher
: Methodsregister
andunregister
can not be called in themiddle of a dispatch
React
added as peer dependency toflux/utils
dist/FluxUtils.js
alongsidedist/Flux.js
Note: This is marked as a breaking change due to the large number of small
changes in
FluxContainer
. Depending on how coupled code is to the timing ofcomponentWillMount
,componentDidMount
, or setting state synchronously it ispossible that there may be some breakages. Generally it should not be an issue.