Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@typeonce/effect-machine-devtools@0.35.0

Minor Changes

• e72b7f5: Declare initial edges and data together in .handle. Remove initial from Machine.state, remove initial and initialConfiguration from Machine.make, and move shared startup data into the root handler's root value or input callback. Each compound declares initial: { target, data? }; parallel handlers use an initial map of region data. Initial targets must be direct children and remain inspectable without executing constructors.

  const root = Machine.state({ states: { Locked: {}, Unlocked: {} } });
  const targets = Machine.targets(root);
  const machine = Machine.make({
    root,
    events: Machine.events({ Coin: {} }),
  }).handle({
    initial: { target: targets.root.Locked },
    states: { Locked: { on: { Coin: { target: targets.root.Unlocked } } } },
  });

  Replace declarative from callbacks with data, which accepts literals or callbacks. Supply already-decoded values with { decoded: true, data: valueOrCallback }. For root or region data that itself contains decoded: true and data fields, use a callback returning the ordinary schema input. Bound branch and history builders retain .from and .decoded. Replace command-producing initialize callbacks with entry/exit handlers or invocations; definitions become executable only after .handle captures their initial declarations.

Patch Changes

• Updated dependencies [e72b7f5]
  • @typeonce/effect-machine@0.35.0

@typeonce/effect-machine@0.35.0

Minor Changes

• e72b7f5: Declare initial edges and data together in .handle. Remove initial from Machine.state, remove initial and initialConfiguration from Machine.make, and move shared startup data into the root handler's root value or input callback. Each compound declares initial: { target, data? }; parallel handlers use an initial map of region data. Initial targets must be direct children and remain inspectable without executing constructors.

  const root = Machine.state({ states: { Locked: {}, Unlocked: {} } });
  const targets = Machine.targets(root);
  const machine = Machine.make({
    root,
    events: Machine.events({ Coin: {} }),
  }).handle({
    initial: { target: targets.root.Locked },
    states: { Locked: { on: { Coin: { target: targets.root.Unlocked } } } },
  });

  Replace declarative from callbacks with data, which accepts literals or callbacks. Supply already-decoded values with { decoded: true, data: valueOrCallback }. For root or region data that itself contains decoded: true and data fields, use a callback returning the ordinary schema input. Bound branch and history builders retain .from and .decoded. Replace command-producing initialize callbacks with entry/exit handlers or invocations; definitions become executable only after .handle captures their initial declarations.

@typeonce/effect-machine-react@0.35.0

Minor Changes

• e72b7f5: Declare initial edges and data together in .handle. Remove initial from Machine.state, remove initial and initialConfiguration from Machine.make, and move shared startup data into the root handler's root value or input callback. Each compound declares initial: { target, data? }; parallel handlers use an initial map of region data. Initial targets must be direct children and remain inspectable without executing constructors.

  const root = Machine.state({ states: { Locked: {}, Unlocked: {} } });
  const targets = Machine.targets(root);
  const machine = Machine.make({
    root,
    events: Machine.events({ Coin: {} }),
  }).handle({
    initial: { target: targets.root.Locked },
    states: { Locked: { on: { Coin: { target: targets.root.Unlocked } } } },
  });

  Replace declarative from callbacks with data, which accepts literals or callbacks. Supply already-decoded values with { decoded: true, data: valueOrCallback }. For root or region data that itself contains decoded: true and data fields, use a callback returning the ordinary schema input. Bound branch and history builders retain .from and .decoded. Replace command-producing initialize callbacks with entry/exit handlers or invocations; definitions become executable only after .handle captures their initial declarations.

Patch Changes

• Updated dependencies [e72b7f5]
  • @typeonce/effect-machine@0.35.0

@typeonce/oxlint-plugin-effect-machine@0.35.0

Minor Changes

• e72b7f5: Declare initial edges and data together in .handle. Remove initial from Machine.state, remove initial and initialConfiguration from Machine.make, and move shared startup data into the root handler's root value or input callback. Each compound declares initial: { target, data? }; parallel handlers use an initial map of region data. Initial targets must be direct children and remain inspectable without executing constructors.

  const root = Machine.state({ states: { Locked: {}, Unlocked: {} } });
  const targets = Machine.targets(root);
  const machine = Machine.make({
    root,
    events: Machine.events({ Coin: {} }),
  }).handle({
    initial: { target: targets.root.Locked },
    states: { Locked: { on: { Coin: { target: targets.root.Unlocked } } } },
  });

  Replace declarative from callbacks with data, which accepts literals or callbacks. Supply already-decoded values with { decoded: true, data: valueOrCallback }. For root or region data that itself contains decoded: true and data fields, use a callback returning the ordinary schema input. Bound branch and history builders retain .from and .decoded. Replace command-producing initialize callbacks with entry/exit handlers or invocations; definitions become executable only after .handle captures their initial declarations.