I tried it, but the typing uses some hacks and breaks very easily Also, I hate the system of sending events as strings - ThreadSky

About ThreadSky

thiagolino8.bsky.social • 61 days ago

I tried it, but the typing uses some hacks and breaks very easily
Also, I hate the system of sending events as strings

Comments

I ran into this recently for context that needs to be typed. You can drop down to manual types like Zustand, but it's implicitly recommended you type case the context object. Compromises everywhere

thiagolino8.bsky.social•61 days ago

I much prefer zustand, where instead of subscribing to a specific event you can use a selector to listen for changes to a section of your store
In my opinion, if a code must be executed in sync with an event then that code should live inside the event handler

bholmes.dev•57 days ago

Hm, I don’t think that’s how xstate store works. You observe state with selectors the same way you would in zustand. You can *also* listen for events if you want, but that’s for state persistence or logging purposes

thiagolino8.bsky.social•61 days ago

But of course zustand also has its problems, such as not being able to infer the type of the store, having to declare the actions mixed with the states, no derived state and so on

thiagolino8.bsky.social•61 days ago

In the end I ended up creating my own solution that better meets my preferences and needs, with bindings for react, svelte, vue, solid and preact
I'll publish it early next year probably, after polishing it for general use.

pollen8.bsky.social•57 days ago

I know xstate has useSelector that does this. Iirc xstate store does as well. The demo here looks more about observing and handling async events

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply