Is it anti-pattern to use Component state in Redux?
<p>I currently have my store setup. Various things trigger events to update the store, which updates props downstream. This is really handy when triggering something to make updates in multiple components.</p>

<p>Is it anti-pattern to use state for things no other components care about? </p>

<p>I basically have a component that is a page of a form. Editing the form updates state (ie selecting one option makes other options change). I figure when the user hits save, I will trigger event for store to have the new data. Hitting cancel would just go back to another page so returning later will just repopulate from store state.</p>

<p>Does that make sense?</p>