Fix <StrictMode> warnings

[BenoitClaveau]

Is it possible to replace componentWillReceiveProps because is deprecated to remove React 16+ warning.

[timdorr]

cWRP isn't deprecated until React 16.4. As of this moment, 16.3 isn't even out. We're looking at larger refactors around async stuff in React 17 in #890.

[BenoitClaveau]

cWRP seems to be depreacted.

[TrySound]

@BenoitClaveau Which version of react do you use? It shouldn't happen until 16.4.

[respectTheCode]

This started showing up after updating to react-native 0.54.0.

[respectTheCode]

downgrading to react 16.2.0 doesn't remove the warnings

[TrySound]

I guess the problem is react-native. AFAIK they published package with react alpha which had this problem. Try to downgrade it.

[BenoitClaveau]

under "react": "16.2.0",

[respectTheCode]

The warnings are coming from react-native so downgrading react isn't enough. react-native 0.53 with react 16.2.0 doesn't have the warnings

[TrySound]

Yes, I meant downgrade react-native.

[anonrig]

Downgrading shouldn't be the option, since the latest valid version of react-native does deprecated these functions. Is there a ETA on the change?

[catamphetamine]

getDerivedStateFromProps is easy enough using the react-lifecycles-compat thing which isn't a breaking change.
And context also has a non-breaking polyfill (though only for React 16 which would be a breaking change):
https://github.com/thejameskyle/create-react-context

[Hypnosphi]

@timdorr I would like to make a PR migrating react-redux to new lifecycles using react-lifecycles-compat because I don't want StrictMode to warn me about my Connected components. Does it make sense to you?

I'm surprised I have to mention it on this repo, but this React blogpost says that library authors don't have to wait until actual deprecation happens
https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

The primary purpose of the upcoming version 16.3 release is to enable open source project maintainers to update their libraries in advance of any deprecation warnings.

[gaearon]

Yes, the purpose of 16.3 was to let libraries start migrating before the deprecation warnings.