Thanks Richard and Erik for your input, I am taking this all onboard and
giving it lots of thought. I think the next step for me is to experiment
and refactor my app into a couple of different structures. That should give
me a feel for what works well and what doesn't. Thanks again.
On
If you mean dividing a component into 3 separate files - ie. model.elm,
> update.elm, view.elm , then yeah, that's fine. A single file is too. If you
> have a massive Elm component that you feel is difficult to manage in a
> single file, and splitting it into three pieces will make it much
I feel like I just wrote you a vague response - something I try to avoid.
If you have a specific question about how to build or structure something
in Elm, don't hesitate to ask.
On Wednesday, August 17, 2016 at 12:19:21 PM UTC-4, Oliver Searle-Barnes
wrote:
>
> I've been using Elm for about 4
Oliver, we're currently migrating a large production SPA to Elm - 15+ pages
non-trivial app, drag and drop interfaces, complex data display,
integrating with multiple backends, etc. Not a toy.
Components - the best advice I've heard is to extract view/model/update
> separately, as we've seen
