Thanks. Guess it depends on specific use cases. If one child type is owned by many different parent types (example of button comes to mind) then having the child own the messages makes sense. If on the other hand one parent type can have many different types of children (example: list with many different child types), having parent own the message is probably better.
BTW: Have you seen the Parts library? https://github.com/debois/elm-parts I found it today, and also mentions a specific case of splitting internal messages from messages that parent should respond to. Still trying to figure out how it works and how to apply, but looks like it may be alternative approach to parent-child communication. -- 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.
