Marked deprecated react lifecycles as UNSAFE_*

[rj-david]

As a quick fix to remove the warnings starting react 16.9.0, this marked the deprecated react lifecycles as UNSAFE_*

(Note that this is just to remove the warning. There is still a need to refactor this code to move the code from the deprecated lifecycles to the correct lifecycles - and maybe change some logic)

[DougPuchalski]

Please merge this. These warnings have been around for ages, and they mask real ones that need attention.

[elstob]

@JedWatson Would be great to have this one merged.

[elstob]

@jossmac - You seem to be the last active dev on this repo of late. Is there any chance we can get this PR merged in please?

[rj-david]

Also tagging @gwyneplaine as this seems affecting a lot of developers now

[gwyneplaine]

@rj-david this looks good, thanks for doing this 👌

[elstob]

Thank you @gwyneplaine !

[mvestergaard]

I'm sorry, but I can't help but feel that this is the wrong approach.
Now the deprecated methods are deliberately being used. What happens when react 17.0 rolls around? This will be long forgotten, and you'll be bombarded with bug reports because you are calling methods that don't exist.

Instead these method calls should be replaced with the newer recommended way of doing things.

What is going on with this project? Is it even actively maintained? Simple things like this take ages to get patched.

[rj-david]

@mvestergaard, feel free to do the right approach and submit the PR. I'm fully supporting that move

[ranneyd]

@gwyneplaine can we make a release for this?

[ranneyd]

@JedWatson @jossmac can we get an NPM release for this? All these people will be grateful:

#3720

[jossmac]

@elstob @ranneyd I don't have publishing permission.

[saboya]

@rj-david @gwyneplaine There's a 6-month old open PR for the proper fix for this: #3487

[rj-david]

@saboya fantastic. Will check it once I get the chance.

We now have a couple of options:

• my PR and keep dependencies the same
• saboya's PR and adjust react's min dependency

[gwyneplaine]

apologies for the delay everyone, this has now been published as part of 3.0.5
@saboya I'll have a look at this PR and get it in as soon as I can

[ranneyd]

@gwyneplaine the lib still has this problem:

#3487

https://github.com/JedWatson/react-input-autosize needs to be fixed too

[ranneyd]

JedWatson/react-input-autosize#166

[youluna]

UNSAFE_ aliases were added to React in 16.3.0, is there any other prs to make the lib compatible with React 16.0.0 - 16.2.x ?