← Back to context

Comment by jadbox

8 years ago

mobx-state-tree is really neat and feels like the next step beyond redux. Not having to create explicit event names and 'action dispatchers' is a real boon to DRY. The only issue I've had is more to do with typescript and using mobx-state-tree plus react router... the type definitions and type error messages can get rather confusing to debug.

> Not having to create explicit event names and 'action dispatchers' is a real boon to DRY.

What about an action creator / reducer isn't dry?

  • You have the name of the action and the name of the action creator which essentially represent the same thing. I've never seen a project which had multiple creators for the same action name.

  • in redux there's so much repetition that most of the time you do copy->paste->find&replace entity name.