title: Is having Store getters with Promise an anti-pattern in Reflux
body: <p>I'm getting into reflux and am embracing the single direction flow.</p>
  
  <p>That said, I'm struggling with the idea of Components having to fire an action just to get data from the store. This is in a lot of examples I have seen, but it seems odd when requesting data rather than being informed there is new data.</p>
  
  <p>Here is sorta what I am thinking:
  The <code>Component</code> initializes with a loading state.
  The <code>Component</code> then calls a getter on the <code>Store</code> that returns a <code>Promise</code> with a <code>success</code> callback that populates the <code>Component</code> state with the new data and a <code>reject</code> that populates <code>Component</code> state with an error. If something updates the <code>Store</code>, I continue to <code>listenTo</code> the <code>Store</code>, but my callback is the same <code>success</code> that is used in the initial <code>Promise</code>.</p>
  
  <p>This seems like a straight forward implementation of Promises, but is it an anti-pattern in Reflux? I understand we don't want to mutate data in the <code>Store</code>, but I'm having a hard time seeing why an <code>Action</code> need to be involved in simple getting.</p>
  
  <p>Can someone set me straight?</p>