Thanks again for sharing your thoughts on this. It is one of the hottest topics for the community right now.
Part II was definitely showing the pattern in a clear way. I wish you clarify the ChildMsg type again in the second post for readers. I do not know either how this will scale but it would be nice to experiment also with point-to-point communication and with worse ways of doing the same thing. My hope is to find a simple yet generic way to handle communications. If the child also needs to send Cmd's, would you recommend using `Cmd.Extra`'s library way to unify commands and outgoing messages to parent component? On Monday, June 27, 2016 at 1:42:48 PM UTC-7, Brian Hicks wrote: > > Parents and children communication seems to come up a lot here and in > #general on Slack. I wrote up a summary of my preferred way of > communicating between parents and children: > https://www.brianthicks.com/post/2016/06/23/candy-and-allowances-parent-child-communication-in-elm/ > > and > https://www.brianthicks.com/post/2016/06/27/candy-and-allowances-part-ii-child-child-communication-in-elm/ > . > > The thing I'm concerned with: how well does this pattern scale? Returning > messages from the childs update function is all good, but does it work well > when there are a lot of messages to be returned? Is there a better way to > deal with that, and is there a "smell" that tells you when to switch > patterns? I'm really interested in what the more experienced people here > have done in this circumstance. > -- 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.
