Right now react/no-deprecated warns multiple times over on deprecated lifecycle methods.

This behavior isn't very optimal -- we should file an issue with ESLint and ask them to remove it once a formal warning is added to React.