title: Translating wrapper-/proxy- pattern to redux
body: <p>I am currently investigating reduxjs as a viable framework for an upcoming project.
  There, we migrate from an old solution, which makes heavy use of the proxy/wrapper pattern.</p>
  
  <p>i.e.:</p>
  
  <ul>
  <li><p>there are models which are kept dumb (pojo) intentionally. They only carry data. Let's assume these are tasks </p></li>
  <li><p>Now these tasks are wrapped dynamically with objects that add cross-cutting features like validation and change tracking to them.</p></li>
  </ul>
  
  <p>Now: Whenever the property is changed, in effect, 3 changes to the application state may happen. 
  E.g.:</p>
  
  <ol>
  <li>the "title" property of the task is changed</li>
  <li>as this change is done throught the wrapper/proxy, it detects the change and
  
  <ol start="2">
  <li>a) updates the "haschagnes" field to "true"</li>
  <li>b) and (potentially) adds a validation error to the "validationErrors" list</li>
  </ol></li>
  </ol>
  
  <p>As far as I understand, in Redux, every action should only be handled once and lead to 1 atomic state change.
  However, in this case, it would be up to three changes.</p>
  
  <p>So my question is:
  Is it possible to translate this wrapper/proxy- pattern based approach to a redux style one?
  And if so, how? (Middleware, WrapperReducer, ...?)</p>
  
  <p>Thank you guys!</p>