OvermindDL why not refactor out that part of update as another function? With 
24 and 8 actions per logical system it definitely seems like a separate update 
(& maybe model) would benefit the maintainability.

Also why not keep the action constructors separate? (Room Joined) You can case 
on them easily and to create then when emitting them you can compose them as 
functions or use Html.App.Map. What's the benefit of namespacing them with 

You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to