Absorb noisy state updates from XState so that consumers of ember-statechart-component can have fine-grained updates

Open
#458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start by reading the referenced XState Solid implementation in packages/xstate-solid/src/useMachine.ts, then inspect how ember-statechart-component currently exposes interpreter state to consumers. Compare that approach with the referenced createImmutable concept in ember-resources. Done means consumers can receive fine-grained state updates without noisy interpreter updates.

Written by the indexing model from the issue text.

Description

From this twitter thread: https://twitter.com/nullvoxpopuli/status/1673077290593554434

The solid.js implementation augments the state from the interpreter instance https://github.com/statelyai/xstate/blob/740409e549ea91974b7fa8ef63438341958dafd9/packages/xstate-solid/src/useMachine.ts#L38C29-L38C44

via this createImmutable.

Note that the concept of createImmutable should exist as a util in ember-resources https://github.com/NullVoxPopuli/ember-resources/

Dominant language
TypeScript
Stars
39
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NullVoxPopuli/ember-statechart-component

All issues in NullVoxPopuli/ember-statechart-component

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.