title: Redux nested reducers or normalize state?
body: <p>I'm making a form component with React, and want to store the form(s) and field(s) state with Redux.</p>
  
  <p>So I have a form reducer and a formField reducer.</p>
  
  <p>I first followed my gut feeling and tried nesting the formField reducer in the form reducer. This basically meant having the formField-related switch cases in both the form reducer and the formField reducer.</p>
  
  <p>This felt a bit messy (repeating code), so I read more in the documentation, and found out it is recommended to normalize the state. So I took away the nested formFields and put them at the same level as forms.</p>
  
  <p>This made the reducer nice and clean, but now retrieving the formFields for a specific form feels horrible. I'm basically looping through all the formFields every time and only returning those with the correct "formId" parameter.</p>
  
  <p>The Redux documentation states you should treat the state as a normalized database, but didn't he forget that you don't have the luxury of being able to query for results?</p>
  
  <p>Did I miss anything here? What is the recommended way to solve this?</p>