Access an immutable version of state via subscribers

I mentioned this on irc earlier today. On-demand, synchronous access to the data in the state isn’t 100% necessary in probably 99% of use-cases, but it does make it easier to work with a choo component from the outside.

Example: if someone wanted to access part of the state object (i.e. the data driving a boxcar view) in order to serialize it somewhere else:

const emitter = require('events')()
const app = choo()
app.model({
  state: {
    data: [],
    moreState: [].
    evenMore: {}
  },
  subscriptions: [
    (send, state) => emitter.on('getData', (cb) => cb(null, state.data)
  ]
})
return emitter

Then someone could do:

boxcar.emit('getData', (err, data) => serializeData(data))

[toddself]

Yeah I gave this some more thought last night. It’s a pain to not be able to access state ever, but it’s for the better. It just means if I want some sort of serialization I’m going to have to create it as an option, which keeps things MUCH neater as it is.

[yoshuawuyts]

I feel this might conflict with https://github.com/yoshuawuyts/choo/issues/32; if not programmatically, definitely in the mental model. Perhaps what could be an option is to expose send-action under the hood as app._send / app._getState() or something for the 1% of the time people are interested in this - don’t even feel it’s needed to document, as it def should be avoided generally. Would that work for you?