Separation of construction and configuration about machina.js

[ifandelse]

@estaylorco - I haven't actually run into a use-case yet where I've needed this (separating states/handler config from instantiation), so unfortunately it's not something that machina likely supports out-of-the-box. Just curious - what sort of constraints are driving the separation of the two for you?

The newer machina bits that I'm messing with locally include a "behavioral" FSM approach where state and behavior are separate - and that might fit this use case well. It's slow going because of umpteen thousand other OSS efforts at the moment, but I'm planning to take some time off in December and get through it if I haven't before then....

[estaylorco]

@ifandelse - Actually, it turns out that there's no need for machina to make the separation. I've made the separation myself, separating the creation of the object literal that gets passed into the FSM's constructor, and the instantiation of the FSM itself.

The use case is a consequence of the fact that JavaScript does not allow LHS expressions in object literals:

{
    '/view/changed': function () {}
}

is acceptable, but

{
    messageTopics.view_changed: function () {}
}

is not.

That forces me to do one of two things: a) live with magic strings, or b) construct the object literal using bracketed notation (i.e. events[messageTopics.view_changed] = function () {}), or something to that effect.

I should mention that I'm using machina.postal.