search

react-component / form

React High Order Form Component(web & react-native)
http://react-component.github.io/form/
MIT License
1.81k stars 296 forks source link

Update react-redux requirement from ^4.0.0 to ^7.0.1 #277

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Updates the requirements on react-redux to permit the latest version.

Release notes *Sourced from [react-redux's releases](https://github.com/reduxjs/react-redux/releases).* > ## v7.0.1 > React-Redux version 7 resolves the performance issues that were reported with version 6, and lays the groundwork for us to design and ship a public `useRedux()`-type Hooks API in a later 7.x release. > > The major change for this release is that `connect` is now implemented using Hooks internally. Because of this, we now require a minimum React version of 16.8.4 or higher. > > This release has undergone extensive performance benchmarking, and we're confident that it's the fastest version of React-Redux yet! We've also expanded our test suite to cover a number of additional use cases and scenarios. > > ``` > npm install react-redux@latest > ``` > > For discussion on the reasons for the major version change and the development process, see: > > [issue [#1177](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1177) - React-Redux Roadmap: v6, Context, Subscriptions, and Hooks](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1177). > > For discussion on the possible design of a future public hooks API, see: > > [issue [#1179](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1179): Discussion: Potential hooks API design](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1179) > > ## Changes > > This release should be public-API-compatible with version 6. The only public breaking change is the update of our React peer dependency from 16.4 to 16.8.4. > > > **Note**: `connect` now uses [`React.memo()`](https://reactjs.org/blog/2018/10/23/react-v-16-6.html) internally, which returns a special object rather than a function. Any code that assumed React components are only functions is wrong, and has been wrong since the release of React 16.6. If you were using PropTypes to check for valid component types, you should change from `PropTypes.func` to `PropTypes.elementType` instead. > > ### Internal Changes > > #### Direct Component Subscriptions > > In v6, we switched from individual components subscribing to the store, to having `` subscribe and components read the store state from React's Context API. This worked, but unfortunately the Context API isn't as optimized for frequent updates as we'd hoped, and our usage patterns led to some folks reporting performance issues in some scenarios. > > In v7, we've switched back to using direct subscriptions internally, which should improve performance considerably. > > (This does result in some changes that are visible to user-facing code, in that updates dispatched in React lifecycle methods are immediately reflected in later component updates. Examples of this include components dispatching while mounting in an SSR environment. This was the behavior through v5, and is not considered part of our public API.) > > #### Batched Updates > > React has an `unstable_batchedUpdates` API that it uses to group together multiple updates from the same event loop tick. The React team encouraged us to use this, and we've updated our internal Redux subscription handling to leverage this API. This should also help improve performance, by cutting down on the number of distinct renders caused by a Redux store update. > > #### `connect` Rewritten with Hooks > > We've reimplemented our `connect` wrapper component to use hooks internally. While it may not be visible to you, it's nice to know we can take advantage of the latest React goodies! > > ### Public API Changes > > #### Return of `store` as a Prop > > We've brought back the ability to pass a store as a prop directly to connected components. This was removed in version 6 due to internal implementation changes (components no longer subscribed to the store directly). Some users expressed concerns that working with context in unit tests was not sufficient. Since our components use direct subscriptions again, we've reimplemented this option, and that should resolve those concerns. > > > ... (truncated)
Commits - [`5c69baf`](https://github.com/reduxjs/react-redux/commit/5c69baf817527ee9a742c9dc4d541945cb7d1719) 7.0.1 - [`4bed472`](https://github.com/reduxjs/react-redux/commit/4bed472feed570045749581a470ba2c6b956ec18) Update README - [`608c9c5`](https://github.com/reduxjs/react-redux/commit/608c9c5960924354ed2109bbc3cca9a38ac2e118) 7.0.0 - [`fa58572`](https://github.com/reduxjs/react-redux/commit/fa5857281a37545c7c036fb2499159b865b1c57d) Use Hooks internally (aka 7.0) ([#1209](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1209)) - [`eae14cc`](https://github.com/reduxjs/react-redux/commit/eae14cc92b79dfbc4f37131d31698b3446a9857d) Enable versioned docs ([#1106](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1106)) - [`28adb54`](https://github.com/reduxjs/react-redux/commit/28adb54a863a51ceec9b3f8bf4441080d82dd220) Touch up deps and Travis config - [`8e20a05`](https://github.com/reduxjs/react-redux/commit/8e20a05fd4bc21c9ab66edd1a64d433356cede7d) Update the codecov config to be more forgiving. - [`72ed6db`](https://github.com/reduxjs/react-redux/commit/72ed6db1947913bdd4900b324243c43a490b4c5a) npm install lockfile flapping 🙄 - [`4f3c2e2`](https://github.com/reduxjs/react-redux/commit/4f3c2e22ffccd54218e95d634811851e3636f087) Replace double whitespaces with single once in the custom store warning messa... - [`471cb2c`](https://github.com/reduxjs/react-redux/commit/471cb2c130a3c423259783fec71eeb516dcb3125) Change CommonJS Broken Docs Link ([#1198](https://github-redirect.dependabot.com/reduxjs/react-redux/issues/1198)) - Additional commits viewable in [compare view](https://github.com/reduxjs/react-redux/compare/v4.0.0...v7.0.1)


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
dependabot-preview[bot] commented 5 years ago

Superseded by #280.