devanshj / txstate Goto Github PK

• txstate right now assumes the machine definition is a literal, in case it's not like initial: Math.random() > 0.5 > "a" : "b" thing most probably will malfunction, so gotta do something about that
• Make all custom error use A.CustomError
• Transitions...
  • Support [{ target: "x" }, "y"] Edit: Ugh isn't this already supported? TODO: check
  • Disallow stupid stuff like
    • { target: [] }
    • [{ target: "a" /* no guard */ }, { target: "b" }]
    • internal: true for strictly external transitions
    • more...
• When an required property is missing the errors are horrible, try showing custom errors for those cases too
• Guarded recursion. Sometimes in an errored machine the recursion becomes infinite to prevent that we'll recurse with a fixed limit

Mainly all functional properties turn into unknown in the return type, more precisely the return type of createMachine is Machine.Of<MachineDefinition.Of<D>> instead of Machine.Of<D> (even if there are no errors in the definition)

(incomplete list)

• createMachine
  • MachineDefinition
    • #12
    • #32
    • #33
    • #34
    • #35
    • #36
  • StateNode
    • #10
    • #11
    • #28
    • #13
    • #14
    • #15
    • #38
    • #16
    • #17
    • #18
    • #20
    • #21
    • #22
    • #23
    • #24
    • #25
    • #37
  • Transition
    • #29
    • #30
    • #31
  • MachineImplementations

See here

Right now initial can only be an identifier of one the child states, but starting from v5 initial can be { target, actions } too

• Support [{ target: "x" }, "y"]
• Disallow stupid stuff like
  • { target: [] }
  • [{ target: "a" /* no guard */ }, { target: "b" }]
  • more...