What if it was only actions?

I am rewriting parts of the documentation and currently revisiting the eternal reducers Vs effects.

Why do we need to force users to think about reducers and effects instead of just actions?

If an action returns a promise, we know it’s an effect, otherwise it’s a reducer.

app({
  model: {
    counter: 0,
    waiting: false
  },
  actions: {
    add: model => ({ counter: model.counter + 1 }),
    toggle: model => ({ waiting: !model.waiting }),
    waitThenAdd: (model, actions) => {
      actions.toggle()
      return new Promise(resolve => setTimeout(_ => resolve(), 1000))
        .then(actions.add)
        .then(actions.toggle)
    }
  },
  view: (model, actions) =>
    <button
      onclick={actions.waitThenAdd}
      disabled={model.waiting}
    >
      {model.counter}
    </button>
})

The only drawback is that Promises are not supported in IE11, so obviously we can’t change this right now.

[nichoth]

@dodekeract Isn’t that how it works currently? You can just call multiple actions from within an action, don’t return anything.

effects: {
    asyncThing: function (state, actions) {
        actions.startRequest()
        fetch(function (err, resp) {
            if (err) return actions.error()
            actions.resolve()
            actions.setState(resp)
        }
    }
}

[nichoth]

Ok, it sounds like it is a style thing. I generally prefer callback hell over new language syntax.