V5 beta breaking change? createMachine<ContextType,EventType, StateType> complains about numbers of generic arguments!

[Simonl9l]

Is there the need for additional "breaking change" documentation for v4?

With v4 one could provide typescript types for the Context, Events and States. However I now get a Typescript error, that the declaration now requires 10 not 3 generic parameters?

I initially followed this youtube vue3 tutorial - where they declared these type outside.

I was looking to see if I can switch this to use the types: declaration per this, but it does not seem to have an element for states"?

Also in the tutorial, one had the option to define a different context type for each state and leverage typescript intersection types.

type MyContext = {
  myContext: string | undefined;
  myOtherContext: int | undefined;
}

type OtherStateContext = MyContext & {
  myContext: string | undefined;
  myOtherContext: int;
}

type InitialState = { value:'Initial'; context: MyContext }
type OtherState = { value:'Other'; context: OtherStateContext }

type MyStates =
 | InitialState
 | OtherState;

type MyEvents =
  { type: "start" } |
  { type: "stop" } |
  { type: "etc };

export const myMachine = createMachine<MyContext, MyEvents, MyStates>({
  id: "my_machine"
...});

how is all this achievable in V5

As an asside I pinged the xstate-pinia folks to see if they were planning to support V5.... wobsoriano/pinia-xstate#3 (comment)

[davidkpiano]

You should not have to provide any generic types.

This should look like:

export const myMachine = createMachine({
  types: {} as {
    context: MyContext;
    events: MyEvents;
    // state types not supported right now
  },
  // ...
});

[Simonl9l]

@davidkpiano thanks (on multiple fronts - xstate-pinia! too)

Ok I figured as much...(video was prob not the nest starting point even for v4 - it was a vue3 example as they seem fairly thin on the ground)!

How far out aprox. is states: support?

Thanks again!

[davidkpiano]

States support will likely be either Typegen unless we can figure out a way to make it work with normal TypeScript. @Andarist has been looking into this.

[Andarist]

There are multiple tiers of the potential states support. So far we bump into TS limitations when it comes to even providing the most basic one 😅 So I'd say that "typestates" support is pretty far away right now. We are constantly evaluating our options here and I'm trying the weirdest things to get something working but it just proves to be quite challenging.