Massimiliano Mirra

@mariusandra @skabbes thanks for merging #282. I just updated and, though I think the mechanism of the crash is the same, the triggered code path for feature flags is different:...

I think I'm missing some important pieces of the puzzle. I thought that the mode of operation is: 1. receive change notification 2. receive change notification 3. receive change notification...

I did a quick test by applying a one-line hack in `aggregator.go` to switch from seconds to milliseconds, and left `fsWatcherDelayS` at the default value of 10. I must say...

Reproducible with Chromium 103: 1. start browser window A with a YouTube video 2. start browser window B in another Sway tab or workspace 3. interaction in browser window ]...

@emersion never said there was one; I wrote: "The _browser_ Page Visibility API tells a page when it's not visible". (https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API) I mentioned it because it helps confirm that the...

Indeed, now that you mention it the second case is something I found myself wishing as well. I did work around the lack of it by e.g. casting event types,...

I haven't dealt with that directly (I've used nested machines rather than nested states), but according to the [Typestate section](https://xstate.js.org/docs/guides/typescript.html#typestates) in the docs: > A Typestate is an interface consisting...

> Got a POC working here: > > #28 > > This should work with the current Typestate API. It doesn't yet handle the `state.matches` use case yet. Does XState...

@davidkpiano no. I've reproduced it in [this sandbox](https://codesandbox.io/s/hardcore-taussig-0xpnh?file=/src/App.tsx) , forked from codesandbox.io's React+TypeScript sandbox — there's actually a typing issue even before any attempt at type narrowing — but the...

@davidkpiano oh, wait, is 1.0.0-rc.4 @next? If so, then it works with @next.