That was what I was thinking, put all the application state in one model, and all updaters will deal with that single model, instead of each Updater having its own sub-model. In the end, almost all the data is dependent somehow.
tirsdag 21. mars 2017 12.22.15 UTC+1 skrev Fedor Nezhivoi følgende: > > > for example the User Profile model might need data from the Session model > > This is probably the biggest issue with how people used to do it in Redux. > If you read it closely then you'll see that your data is dependent. By > separating it between modules you do not make it in decoupled, you just > create more boilerplate and complexity in how it works together. This was > one of the reasons Redux discarded `waitFor` mechanism from Flux. If you > have dependent data just put it in one reducer, that's it. I guess this > pretty much applies here for Elm as well. > -- 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.
