Saving/restoring machine state between runs

Is there any better clear strategy of saving and restoring machine state between instances than saving state() and restoring with force_transition()?

I am currently using mentioned above methods, but the only drawback I see if that I do not save/restore any data besides states, and also force_transition() is causing entry hooks to fire up, which doesn’t make any sense as they have already been fired up in previous run.

[xtovski]

Yes, you are correct. I am re-binding all hooks in a state machine factory I made to do all serialization/de-serialization tasks.

[StoneCypher]

@xtovski - draft implementation available, please update. API should be stable.

const machine_string = "a 'next' <-> 'next' b;";

const foo = jssm.from(machine_string, { history: 5, data: 2 });

foo.do('next'); 
foo.do('next'); 
foo.do('next'); 

const ser = foo.serialize();

const bar = jssm.deserialize(machine_string, ser);