Update init behavior

[jamesplease]

This PR has two commits that to do two separate things:

de98e12
This updates #11 to fully fix #9 by taking sideEffects into account. It ensures that the sideEffects from init replace any sideEffects set up in initialState.

5ff7362
This is slightly tangential but it renames the newSideEffect argument to be sideEffects. This makes it so that the update shape mirrors the internal state.

Previously, the shapes were:

// Update
{
  newState,
  newSideEffect
}

// State
{
  state,
  sideEffects
}

After this commit, the shapes are:

// Update
{
  state,
  sideEffects
}

// State
{
  state,
  sideEffects
}

I think this naming change makes sense in light of #10 . Users should only need to think about having one state imo.

---

I tested and this seems to be working in my app where I'm using this lib.

[jamesplease]

We may not want to fall back to prevState.state this when this fn is called from init...what do you think @conorhastings ?

[conorhastings]

i think you're right, the side effects can return a valid null state or 0 state

[conorhastings]

i think if we just change this, tthis and compose are good to go, tried itt out in sample app

[conorhastings]

thanks for making this so much better lol

[conorhastings]

have interview during day, will review all tonight

[jamesplease]

No rush at all! Good luck today👌

[conorhastings]

closed by #19