You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand it correctly Messages are thrown away when they come from the channel and are directly being processed/mutated on to the app atom. Would it be interesting to take a more reactive approach here: keeping the messages instead and reduce over the messages to get the current state like in Elm? This gives a more flexible/reproducible history and allows you to for instance hot swap the processing protocols and see history change with it (like in the time travelling debugger). Planning to give it a try myself in the next coming days, but would love to have your ideas/opinion upfront.
The text was updated successfully, but these errors were encountered:
If I understand it correctly Messages are thrown away when they come from the channel and are directly being processed/mutated on to the app atom. Would it be interesting to take a more reactive approach here: keeping the messages instead and reduce over the messages to get the current state like in Elm? This gives a more flexible/reproducible history and allows you to for instance hot swap the processing protocols and see history change with it (like in the time travelling debugger). Planning to give it a try myself in the next coming days, but would love to have your ideas/opinion upfront.
The text was updated successfully, but these errors were encountered: