Design a simple and intuitive support structure with redux.

[sstephens]

This is for open discussion and ideas and best practices.

[sstephens]

According to Redux docs, under Basic Reducer Structure, reducers can usually split into 3 categories:

• Domain data: data that the application needs to show, use, or modify (such as "all of the Todos retrieved from the server")
• App state: data that is specific to the application's behavior (such as "Todo #5 is currently selected", or "there is a request in progress to fetch Todos")
• UI state: data that represents how the UI is currently displayed (such as "The EditTodo modal dialog is currently open")

I would like to make all data that falls under the Domain category reside in a separate module that can be imported through NPM and reused in other applications like the equipment app.

Then the time-keeping app and the equipment app can build upon that main setup to customize any other App and UI states that is may need.

[sstephens]

Normalizr is a tool for defining data schemas with nested relationships. busybusy usually doesn't return nested data, however, the relationships still exist in the data. I think this would be a great tool to help us define our model layer.