Ensure actions are executed from a restored initial state.

[davidkpiano]

The issue was that when restoring from an initial state, state.actions weren't being resolved against the specified machine.options.actions action mapping, so actions weren't being executed.

Fixes #1174

[changeset-bot]

🦋 Changeset is good to go

Latest commit: 5b0c2f4

We got this.

This PR includes changesets to release 7 packages

Name	Type
xstate	Minor
@xstate/analytics	Major
@xstate/graph	Major
@xstate/immer	Major
@xstate/react	Major
@xstate/test	Major
@xstate/vue	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 5b0c2f4:

Sandbox	Source
infallible-mcnulty-88pz5	Configuration
flamboyant-pond-jor2k	Configuration

[Andarist]

I'm having second thoughts - actions are being considered fire and forget, so this is very likely that actions for a particular state has already been executed and only after that the state has been persisted and rehydrated later. In such a case action would be fired twice - which is not necessarily always a good thing. It should be up to a developer to decide about this because we don't know what's their strategy for persistence & rehydration.

[davidkpiano]

Regardless, this PR is still correct, because there is a bug where actions aren't being resolved correctly, even though they should. The fix is general.

The behavior of whether or not those resolved actions should be executed is a separate issue, but I agree, it should be addressed.

[Andarist]

👌