title: How to pass props to react-router 1.0 components?
body: <p><strong>Please note, that although the question itself is largely a duplicate of <a href="https://stackoverflow.com/questions/30871070/react-router-pass-props-on-routes-to-child-components">this</a>, it concerns a different version which <em>should</em> support this. The linked question already accepted an answer on an old version</strong></p>
  
  <p>I'm pretty confused about what the intended workflow is.</p>
  
  <p>Let's say I have a menu system where clicking on each item uses react-router to navigate to an area which pulls some data from the server.</p>
  
  <pre><code>url: yoursite/#/lists/countries
  ----------------------------
  Billing Codes | &lt;&lt;Countries&gt;&gt; | Inventory Types 
  ---------------------------------------------------------
  Countries:
  ---------------
  Afghanistan
  Azerbaijan
  Belarus
  </code></pre>
  
  <p>with routes something like</p>
  
  <pre><code>Route #/lists component: Lists
     Route billing-codes component: BillingCodes
     Route countries component: Countries
     Route inventory-types component: InventoryTypes
  </code></pre>
  
  <p>I don't want to preload data from the server until an area is navigated to, so in my <code>Countries</code> component's on <code>componentWillMount</code> I fire an event (I'm using reflux but...whatever) that triggers a store to do an ajax request and update itself with the current list of countries.</p>
  
  <p>Now the <code>Countries</code> component reacts to that change in state by updating the countries in its props. Except - reasonably - that generates an invariant error because I shouldn't be updating props on a child component, I should update it at the top level. But the top level is the router itself so now I'm just lost - where <em>am</em> I supposed to listen to changes and update props from?</p>
  
  <p>(<a href="https://github.com/rackt/react-router/issues/1472" rel="nofollow noreferrer">Cross-posted to the issue tracker</a> as I think it needs some clearer documentation)</p>