Weird dispatch issue with useElmish

[forki]

Weird dispatch issue with useElmish

[forki]

this actually makes a lot of sense and I wonder why it ever worked before.

anyways sorry about the noise and many thanks for the help to spot the obvious!

[alfonsogarciacaro]

@Zaid-Ajaj If I replace Feliz.UseElmish with Fable.React.UseElmish Elmish subscriptions work. Haven't checked what's the actual difference (maybe because Fable.React.UseElmish doesn't use the useSyncExternalStore polyfill?)

Test project: https://github.com/alfonsogarciacaro/app

[alfonsogarciacaro]

Generated code looks right. By debugging I found that the dispatch reference captured by subscribeToTimer becomes invalid. Not sure if there's something funny going on or this how useSyncExternalStore is supposed to work (React has this oddities).

You have two options:

1. Pass dispatch as a dependency to useEffect. This is actually what React recommends, any captured value must also be a dependency.
   React.useEffect(subscribeToTimer, [| box dispatch |])

2. Use Elmish subscriptions

☝️ Forget about the 2nd option, I tested and in that case the subscription is registered twice. Not sure why.

[Zaid-Ajaj]

this actually makes a lot of sense and I wonder why it ever worked before.

It could be that previous version gave you a stable dispatch (the view and the effect get the same dispatch, always)

Sometimes to avoid capturing, I use inline (i.e. let inline subscribeToTimer()) so that the body of the effect is inlined and doesn't capture but that might not work with effects as subscriptions. I used that often with React.useMemo

[Zaid-Ajaj]

@alfonsogarciacaro I am not sure, will have a look! First thing I need to do is actually bring back tests to life to ensure expected behaviour, will try when time permits