> However, the downside of doing passing the entire model everywhere is that > you have to keep the entire model in your head when looking at any of your > view functions.
This is correct, but how can you avoid passing the whole model to all views if the data model isn't structured similarly to your view hierarchy? The idea of doing pre-processing on your data into a view-friendly structure seems to add overhead and complexity, while also more or less duplicating your view structure in two places: the view stack, and the view data. We have found that as apps grow in size, it is unreasonable to couple a data model's internal structure to the requirements of a UI, and thus passing The whole model is the only valid option for most view functions. The exception are leaf nodes down the line that have few or no children, in which case they can receive focused inputs only. -- 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.
