React-redux-firebase: bug(HOCs): use of componentWillReceiveProps in HOCs cause warnings with 16.9.0

[shevchenko0]

Bug report

Steps

Use firestoreConnect with [email protected] and [email protected]
Open your console to see the warnings

Expected Result

No warnings should appear

Actual Result

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: FirestoreConnectWrapped(Connect(withI18nextTranslation(TranscriptsList)))

Version

3.0.0-alpha.16

[prescottprue]

Wasn't able to go straight to componentDidUpdate, but that will most likely happen in the future to support v17 of react.

The warning is fixed in the v3.0.0-beta release.

[s4ek1389]

@prescottprue Still getting this warning when using Strict Mode in react: 17.0.1 and react-redux-firebase 3.7.0. Is there a way to fix it?

[prescottprue]

@s4ek1389 Can you open a new issue with the warning so we don't loose track

[LuisMerinoP]

I am getting the warning with "react": "^17.0.1" and "react-redux-firebase": "^3.10.0". I opened an issue.
This is the code producing the warning:

[export default compose<React.FunctionComponent>(
  connect(mapStateToProps),
  firestoreConnect([
    { collection: 'projects' }
  ])
)(Dashboard);

[nicholas919]

any updates on this issue? i'm getting same warning too

[LuisMerinoP]

no updates. I opened a new issue for this warning. Seems that you should live with it until the HOC is fixed, or use react hooks to link your component to firestore to get rid of the warning

[nicholas919]

great.. thanks for the advice @LuisMerinoP but i think im done with this, the documentation won't help much and still.. errors were keep appear on my console... it would be great to create my own npm package