Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: reduxjs/react-redux
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: reduxjs/react-redux
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 5.x
Choose a head ref
  • 8 commits
  • 6 files changed
  • 5 contributors

Commits on Nov 10, 2018

  1. Configuration menu
    Copy the full SHA
    574ecc5 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    c9d214e View commit details
    Browse the repository at this point in the history
  3. 5.1.1

    timdorr committed Nov 10, 2018
    Configuration menu
    Copy the full SHA
    5cdb83a View commit details
    Browse the repository at this point in the history

Commits on Aug 28, 2019

  1. Use UNSAFE_ lifecycle event names where supported. (#1383)

    This provides forward compatibility with React 17.x for those still
    using the react-redux 5.x series by detecting support for the UNSAFE_
    prefixed lifecycle event names (using `React.createContext` as a feature
    check as it avoids semver checking but was introduced in React 16.3 at
    the same time as the UNSAFE_ prefixes).
    elyobo authored and timdorr committed Aug 28, 2019
    Configuration menu
    Copy the full SHA
    9137f7f View commit details
    Browse the repository at this point in the history

Commits on Oct 1, 2019

  1. Fix React version check to support 16.10 (#1407)

    * Fix React version check to support 16.10
    
    Since `parseFloat(React.version)` resolves to `16.1`, that breaks our version check. So, I've switched to checking against the `forwardRef` API's existence, which was also added in 16.3.
    
    * Also fix the version check in connectAdvanced.
    timdorr authored Oct 1, 2019
    Configuration menu
    Copy the full SHA
    4144715 View commit details
    Browse the repository at this point in the history
  2. In React >=16.3, use unsafe lifecycle methods to avoid warnings, even…

    … in development (#1410)
    samkline authored and timdorr committed Oct 1, 2019
    Configuration menu
    Copy the full SHA
    2978315 View commit details
    Browse the repository at this point in the history

Commits on Oct 8, 2019

  1. Configuration menu
    Copy the full SHA
    ad8d773 View commit details
    Browse the repository at this point in the history
  2. 5.1.2

    timdorr committed Oct 8, 2019
    Configuration menu
    Copy the full SHA
    4be2626 View commit details
    Browse the repository at this point in the history
Loading