David Khourshid

> I filter actor reference can make store context into indexDB work Yes, this is what you should do for now, and is a good workaround. You can also call...

> > > I filter actor reference can make store context into indexDB work > > > > > > Yes, this is what you should do for now, and...

This would be more of a feature than a bug. You can do this manually now: ```js function matchesId(state, id) { return !!state.configuration.find(stateNode => stateNode.id === id.slice(1)); } matchesId(state, '#templates_loading');...

@tklepzig Can you provide a reproducible example for that? > I'm interested as well whether this is by design. The best approach moving forward will be to use **event sourcing**...

The main issue with this is in assuming that a previous invocation should be _restarted_. In many cases, this should not happen because the invocation might be doing some destructive,...

> it only evaluates the assign twice (which is still a problem, especially for something like telemetry or other fire-and-forget API calls) Keep in mind that assign actions should be...

@Andarist Is this good to go?

Should this be tackled in v5 instead, where we have better typings for actions?

Right, this is awesome, but let's make a new `xstate-examples` repository. I'll do that today!

> Hello @davidkpiano, I have been using xstate on my daily work and it is an awesome tool, I would like to contribute, is this issue still available to be...