Calling setState in componentDidUpdate

It might be worth revisiting [react/no-did-update-set-state](https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-did-update-set-state.md).

Now that `componentWillReceiveProps()` is being deprecated, `componentDidUpdate()` is the only "safe" way to detect changes in props and set state accordingly.

The [React docs](https://reactjs.org/docs/react-component.html#componentdidupdate) say calling `setState()` in `componentDidUpdate()` is permitted, albeit with caveats.

> You may call setState() immediately in componentDidUpdate() but note that it must be wrapped in a condition like in the example above, or you’ll cause an infinite loop. It would also cause an extra re-rendering which, while not visible to the user, can affect the component performance.

Start with the linked react/no-did-update-set-state rule documentation and the React componentDidUpdate documentation. Determine what change to the rule or its guidance the issue proposes, then verify the expected behavior against the documented caveats; done requires a decided scope and corresponding project update.

Written by the indexing model from the issue text.