In response to a state change, I want to trigger another state change. Is that inherently a bad idea?
The specific sort of scenario is that the component is modeled as a
No. Please use componentWillReceiveProps instead. It has the same signature of shouldComponentUpdate and you're safe to call this.setState there.
componentWillReceiveProps
shouldComponentUpdate
this.setState