That is precisely how some of it is done (written more recently), the part I showed above was one of the first bits written back when everyone was saying "make model and msg flat!", I do not do that anymore and do need to refactor, but it does bug me how people keep saying to make everything flat instead of separate by logical concerns in the first place...
On Thursday, September 22, 2016 at 11:52:59 PM UTC-6, Joaquín Oltra wrote: > > OvermindDL1 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 underscores? > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
