Mark componentWillReceiveProps UNSAFE

[y6nH]

See #66. This is the minimum change required for React 17 compatibility. The warning thrown by React 16, for reference:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. 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
      * 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.

[marsonmao]

This has to be fixed error: Identifier 'UNSAFE_componentWillReceiveProps' is not in camel case (camelcase) at src/index.tsx:173:3:; guess that adding a eslint disable next line?

[y6nH]

Now it's really broken. I suspect we have to update dependencies.

A one-liner is never a one-liner.