Hi!
I'm writing here, as this probably doesn't fit within a tweet :).
I was working on a bigger redux app not too long ago, where I had a lot of entities with relationships in between. The "store layer" was mostly concerned with fetching data, storing them, providing ways to create/update/delete them via REST and in more sophisticated scenarios optimistic updates, cancelling duplicate requests when data was fetched just recently or currently being fetched and paginating through lists.
As there is usually no special logic in regards to the type of an entity, I was trying to put together an abstraction layer for the actions, the reducers and the selectors so that doesn't have to be repeated all the time.
For data from endpoints like /user
(only 1 instance) or /books
(a list) this has worked quite well, but it became somewhat complicated with nested entities that have relationships. My wrapper offered a configuration to specify what kind of entities are related in what way (either 1:1, 1:n or n:m; e.g. `