States which act as a second possible initial state should not be marked as unreachable

[mattpocock]

I might want to start my machine in one of two possible initial states. I don't want a warning that this state is unreachable.

Another way to do this might be to be able to dismiss alerts on states.

[Andarist]

A better pattern would be to allow initial transitions to select the actual initial state. This way the selection logic would be encoded in the machine which would be a good thing from the modeling PoV.

[davidkpiano]

A better pattern would be to allow initial transitions to select the actual initial state. This way the selection logic would be encoded in the machine which would be a good thing from the modeling PoV.

How would this look? (Pseudocode welcome)

[Andarist]

createMachine({
  initial: [
    {
      guard: ({ event }) => event.input.isServerEnabled,
      target: "enabled",
    },
    {
      target: "disabled",
    },
  ],
  states: {
    enabled: {
      on: {
        TOGGLE: "disabled",
      },
    },
    disabled: {
      on: {
        TOGGLE: "enabled",
      },
    },
  },
});

IIRC we don't currently support this at runtime but we totally could support it. It's also something that is supported by SCXML and I think it makes a lot of sense to support this. It shouldn't also be a big problem figuring out how to visualize this.