xstate-tree machine building 2.0 about xstate-tree HOT 3 CLOSED

After thinking about this on the weekend I think the solution is actually fairly simple. The only important splitting-up factor is being able to have the machine and view in separate files. Actions/selectors just don't get big enough that it matters where they end up.

But splitting out the view is hard because it needs types from the machine to be able to generate the props. The machine however is already totally independent. Which means it makes sense to instead only require the machine can be in a separate file, and the view/selectors/actions to be defined together, with the ability to omit the selector/action/slots if they aren't required.

So I propose something like

// machine file
// slots need to be defined with the machine as that is where they are used
export const someSlot = singleSlot("whatever");
const machine = createMachine();

// xstate-tree-machine file
import { machine, someSlot } from "./machine";

// name needs some bike shedding
export const SomeMachine = createXstateTreeMachine(machine, {
  slots: [someSlot],
  // selectors could be omitted, in which case they would default to the machines context, ie equivalent to
  // selectors: ({context}) => context,
  selectors: ({context, inState, canHandleEvent}) => ({ something: context.something + context.someOtherThing }),
  // actions is omitted so it resolves to an empty object, equivalent to
  // actions: () => ({}),
 view: ({ selectors }) => <p>{selectors.something}</p>
})

Then to enable access to the selector/action/view functions there can be a set of utility functions like retrieveView(machine), retrieveSelectors(machine) so you can pull them out for use in stories/tests etc. And they could also provide some utilities for generating things like the inState prop that requires specific types.

from xstate-tree.

🎉 This issue has been resolved in version 4.1.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from xstate-tree.

🎉 This issue has been resolved in version 4.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from xstate-tree.