The visibility component is using UNSAFE_componentWillReceiveProps . This now gives a warning.
馃憢 Thanks for opening your first issue here! If you're reporting a 馃悶 bug, please make sure you've completed all the fields in the issue template so we can best help.
We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
this is a bug
Similar issue using a Tab component. In a clean environment with an empty (or not) <Tab /> we get:
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles 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
Please update the following components: Menu, Tab
@levithomason @layershifter now that React has changed these UNSAFE_* lifecycle methods to show as warnings in newer versions of React, I think it would probably be good for us to go in and update these. componentDidUpdate or possibly getDerivedStateFromProps I believe are the recommended method to reach for in these scenarios. I did not see anything in progress or noted stating that we want to work on this... but I may have missed it. Thoughts?
Other areas we are using this lifecycle method:
For anyone else landing here... this is a dev mode only warning and lifecycle methods will continue to function in React 17+ with the UNSAFE_ prefix.
Was fixed in [email protected] 馃帀
Most helpful comment
Was fixed in
[email protected]馃帀