Update dependency flux to v4 #16
Open
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.1By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
facebook/flux (flux)
v4.0.1Compare Source
fbemitterdependency to 3.xv4.0.0Compare Source
fbjsdependency to ^3.xv3.1.3Compare Source
v3.1.2Compare Source
v3.1.1Compare Source
v3.1.0Compare Source
Dispatcher: Methodsregisterandunregistercan once again be called inthe middle of a dispatch.
v3.0.0Compare Source
FluxMapStore: Removed. It added very little value overFluxReduceStore.FluxContainer: Subscriptions are setup in constructor rather thancomponentDidMountFluxContainer: Can create containers using stateless functional componentsFluxContainer: Uses functional version ofsetStateFluxMixin: Subscriptions are setup incomponentWillMountrather thancomponentDidMountDispatcher: Methodsregisterandunregistercan not be called in themiddle of a dispatch
Reactadded as peer dependency toflux/utilsdist/FluxUtils.jsalongsidedist/Flux.jsNote: 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.