Merge hooks and subscriptions into "events".

I’d like to simplify the API a bit more without losing functionality / power or compromising speed. I think this is possible by removing subscriptions and hooks and introducing a new concept: events.

app({
  events: {
/* replaces subscriptions*/
    onLoad: [ (state, actions), ... ], 
/* below are the hooks you already know */
    onAction: [ (state, action, data), ... ], 
    onUpdate: [ (oldState, newState, data), ... ],
    onRender: [ (state, actions, view), ... ],
    onError:  [ (state, error), ... ]
  }
})

• Newcomers have a concept less to learn and a single signature to remember when using events.
• Easier for plugins to add new events, for example the Router and onRoute.

Example 1

Before

app({
  subscriptions: [
    (model, actions) => actions.doSomething()
  ]
})

After

app({
  events: {
    onLoad: (state, actions) => actions.doSomething()
  }
})

Example 2

Before

app({
  hooks: {
    onAction: (action, data) => console.log(action, data)
  }
})

After

app({
  events: {
    onAction: [
      (state, action, data) => console.log(action, data)
    ]
  }
})

[zaceno]

👍 for the idea of mergeing subscriptions and hooks into "events.

I basically like @dodekeract’s signature normalization, except I think perhaps:

a) If we give all events the model (the current model) as first argument, then onUpdate doesn’t need new in the second argument

b) Wouldn’t it make sense to provide the “error” function to all the events as well (except for onError of course 😉 ) ?

[FlorianWendelborn]

@jbucaran Can this be closed?