The problem i see with this approach is that in hierarchy of deeply nested components, the whole ancestry would need to know about the intention of the leaf. I was hoping towards more of a command-like approach.
> On Dec 2, 2016, at 14:45, Erik Lott <[email protected]> wrote: > > Birowsky, your leaf component will need return messages to the parent, and > the parent can act on those messages to update it's state. There's no magic > to it unfortunately. Do you have a specific problem you're trying to solve? > > On Wednesday, November 30, 2016 at 12:04:08 PM UTC-5, Birowsky wrote: > Hey Eric, please elaborate on this one. How do you envision leaf component > triggering global state update? > > The second problem becomes: how do we load this global state/business data > into the application and cache it? This requirement is now fairly easy to > wire-up in elm since the http requests and data cache all live at the same > level of the application (the top level). If anyone wants more details on how > to do this, let me know. > > > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Elm Discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elm-discuss/j-Wa6NGiYUM/unsubscribe > <https://groups.google.com/d/topic/elm-discuss/j-Wa6NGiYUM/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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.
