Prepare for upcoming react deprecations introduced in 16.3

[justinobney]

Suggestion: begin migration to new react lifecycles while retaining backwards compatibility via react-lifecycles-compat

Example: https://www.youtube.com/watch?v=G9S1IghlkCI

Steps

• Use new lifecycle methods introduced in react 16.3 in a component that renders react-semantic-ui components.

Expected Result

• React does not log errors/warning about upcoming deprecations to the console.

Actual Result

• React IS logging errors/warning about upcoming deprecations to the console.

Version

0.79.1

Testcase

[welcome]

👋 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.

[levithomason]

@justinobney this is great, could you start a PR for this?

[joshuaobrien]

Is this up for grabs? I'm happy to do it.

[justinobney]

@joshuaobrien that would be great. I doubt I could get to it for a few weeks.

[joshuaobrien]

I'm on it. Will get started on the weekend :)

[msrikanth508]

I would like to start on this, Couple of life cycle methods are marked as UNSAFE in 16.3 and two new methods getDerivedStateFromProps, getSnapshotBeforeUpdate got introduced. @levithomason what exactly do we need to do?

[joshuaobrien]

Hi @msrikanth508, I am working on this at the moment. What we need to do is refactor the components that use the deprecated methods so that they no longer use them. Functionality that was in these deprecated lifecycle methods needs to be moved into other lifecycle methods.

My experiences so far is that these changes are not always clean cut. Also, changes to tests are likely required to accommodate the new methods.