react-redux notes

[buhman]

• It seems slightly obtuse to have to define both actions and reducers
• there's an obvious pattern for crud interfaces, where you have:
  • thunk action
  • api action
  • reducer action(s)
  • reducer
  • components
  • containers
  • components that are also containers?
• it would be nice if there were a framework that enforced this "good style", and reduced repetitiveness

Other problems are more related to javascript itself (maybe there's precedent for some compile-to-js + react stack):

• state changes are awkward to write:

    case 'DELETED_SHORT':
      return Object.assign({}, state, {
        fetching: {
          ...state.fetching,
          [action.fetch]: false
        },
        items: state.items.filter(item =>
          item.id !== action.id
        )
      })

• select case seems so primitive compared to pattern matching
• some projects make strange sets of const THIS_THING = 'THIS_THING'
  • atoms are so much less bloat

Overall, I like it much more than jquerypocalypse, but it seems like better things should exist.

[buhman]

Things that I might try later:

• writing tests for react components and reducers
• adding another bounded context for an unrelated operation