title: Should I reset my redux store on each router navigation?
body: <p>I'm using Angular to write my application, and I use <strong>Redux</strong> through <strong>ngrx/store</strong> to store my application state.</p>
  
  <p>Everything work fine, but now that my application get pretty large, I came with the following observation:</p>
  
  <p>For nearly each page/resource, I use a different resolver that fetch from my backend, all the data necessary to correctly display and act on this particular page.</p>
  
  <p>This resolver allow me to make this page independent from the previous state of the application.</p>
  
  <p>So if the application is loaded and started from, let's say:
  <a href="https://myapp.com/resourcetype1/resourceId" rel="nofollow noreferrer">https://myapp.com/resourcetype1/resourceId</a></p>
  
  <p>The resolver will load the <strong>resourcetype1</strong> with id <strong>resourceId</strong> in order for my page to work out of the box.</p>
  
  <p>Knowing that, <strong><em>I was wondering if it could be a good idea to fully reset my  redux store on each router navigation start</em></strong>.</p>
  
  <p>I think this could have two benefits:</p>
  
  <ul>
  <li>Provide a cleaner redux store without residual data from a previously executed page.</li>
  <li>Provide an empty store before each 'page display', which could help to detect when a page is using data from a previously loaded page (and so which would have crashed if loaded 'directly' using its urm).</li>
  </ul>
  
  <p>So the questions are:</p>
  
  <ul>
  <li>What do you think about this reflexion?</li>
  <li>What are your habit concerning that?</li>
  <li>Are you resetting your redux store at some point or no?</li>
  </ul>