On Wednesday, March 29, 2017 at 8:54:13 PM UTC+1, Mark Hamburg wrote: > > My advice would be to use the message routing patterns from classic TEA in > the places it makes sense to break ones app apart — just know that it isn't > particularly well suited to building components. >
I have to say, I am using nested TEA and I am finding that it is very good for building components. What I like is that it gives a standard structure to each of my components: (Msg, Model, init, subscriptions, update, view). I am using Cmd.map and Html.map and Sub.map to wrap the messages of a component so that it can be embedded within the message type of the thing importing the component. There is a little bit of boiler-plate to 'lift' the component into a parent - but you can write helper functions for that. -- 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.
