title: Purely following Redux way and having Dump | Presentational components
body: <p>When you create React components, do you mostly follow the philosophy of only having dump/presentational react components that are connected to Containers? Only having dump components fulfils one of the main principles of redux (single source of truth) but complicated things when it comes to component isolation. By that i mean that: </p>
  
  <p>... i end up have a table component which can present data and have the ability to select rows, but selection don't work unless its connected to the store via a container. This is good in <em>theory</em> because a lot of other components rely on that selection so having everything going through the store keeps <em>everything in sync</em>. However, it means that the table component cannot be fully interactable by itself (selection won't work if its not connected to the store). This could make automated UI tests slightly harder to test as each component will need to have a related container in order to work properly. </p>
  
  <p>Another example; say that you have a dialog box, would you have the show state within the component itself or have it connected to the store through a container?</p>
  
  <p>Any thoughts?</p>