this._data is never set when without hooks path is taken in transition_impl

[WNemencha]

jssm/src/ts/jssm.ts

Lines 2362 to 2380 in 7de448c

	// or without hooks
	} else {
	if (this._history_length) {
	this._history.shove([ this._state, this._data ]);
	}
	this._state = newState;
	// success fallthrough to posthooks; intentionally no return here
	// look for "posthooks begin here"
	}
	// not valid
	} else {
	return false;
	}

Code in this extract should change to something like:

+       this._data = newData || this._data; // or better logic not sure about this.

        if (this._history_length) {
          this._history.shove([ this._state, this._data ]);
        }

        this._state = newState;

otherwise when not using hooks, and calling .data() it always return null, also data does not appears in history.

[StoneCypher]

Sorry, took me a second to see this. In the future, I'll see it faster if you use the unified tracker.

I'm now trying to think my way through this problem.

[StoneCypher]

Confirmed. Resolution will continue on StoneCypher/fsl#1259

Thank you, @WNemencha

[StoneCypher]

data argument for transition, action, go, do via transition_impl wasn't actually wired up. it looked like it was, because the data return value from hooks was and they go through the same mutual implementor.

You were right that the call pattern had to be implemented without hooks, but I also had to implement the call pattern with hooks.

This led to noticing that at this time, there is also no way practical way to set data to undefined, which will be fixed promptly.

26 tests added to enforce:

1. a common sense full cycle without hooks
2. a common sense full cycle with hooks
3. every adjacent pairing of hooks in ordering, to assert that hooks override in the correct order

Thank you, @WNemencha , for improving this state machine. I apologize for this oversight.