Eugene Tolmachev
Eugene Tolmachev
I closed the issue because "make the SyncDispatch more useful to library authors" is not a problem statement, elevating a leaked abstraction is not an option and have multiple dispatchers...
> based on the current state of the model (changable per message) ```elm -- SUBSCRIPTIONS subscriptions : Model -> Sub Msg subscriptions model = if model.sub then Time.every 1000 Tick...
> subscriptions and commands are just objects describing the effect They are defined exactly the same way in Elmish, so no, they are not just describing the effect, I think...
> `fun dispatch -> do crazy sideffect and send msg back` we can both be right: replace that ^ with `Task.doCrazySideEffectAndSendMsgBack` and you get the essence of how things work....
@jwosty Can you see if this can be reimplemented with `Cmd.batch`?
1) You are asking for a change w/o demonstrating the need. As I've mentioned elsewhere logging is a form of data loss and if there's anything we could improve in...
The core idea of Program is composition of its functions, write your own update, init, etc and make new Program instance, same way everything else is done - logging, debugger,...
What's the correct workaround here, if any? IMO #13070 makes the impact much worse than Medium. Answering my own question: use [Ply](https://github.com/crowded/ply) for now and shadow `backgroundTask`: ```fsharp let backgroundTask...
I'm confused, why is this resolved if we're still getting this error in 6.0.6? If this: ```fsharp let stringy
SDK 6.0.403 - doesn't work. SDK 7.0.100 works!