Structured TodoMVC example with Elm

tl;dr: Check out the structured versions of TodoMVC here.
may/2016: Upgrade to Elm 0.17
jun/2017: Upgrade to Elm 0.18

Christian Alfoni wrote a great article about how to structure your Elm app, inspired by that, I decided to refactor the official TodoMVC example by Evan, which has only one file, to split the logic.

To explain why this is necessary, I'll quote Christian:

All examples of Elm applications I have seen is expressed as one single file. That does not work in bigger applications. How does splitting my app in different files affect how Elm works?

The community needs more bigger app examples, and I'll try to help with that using the famous TodoMVC example.

The refactor experience

Before starting, I really need to point out how awesome experience was completely refactoring an Elm app: a joyful, painless experience!

I moved things, I renamed things, I changed the whole app, and on each step the result was always the same: after compiling, the app was still working flawlessly.

It was the most safe refactoring I’ve ever done, thanks to Elm and its powerful compiler.

Splitting the Model

Thanks to The Elm Architecture, it's not very hard to look at our code and see how it should be split, let's just look to the original Model:

It's easy to notice that we can move the Task type to another file, but look closer, and you will notice that there are actually 4 things being handled by this model: the new task being created (using field and uid), the list of current tasks, each task inside that list, and the visibility control.

It's 4 things, and just by looking at the model it doesn't seem very messy, but when we get to the update function, things gets confusing:

This update function does too much. It handles changes on the task list (add, delete), new task entries (update field, add), visibility changes and changes for each Task inside the list (noticed how we repeated “let updateTask t = if…” 3 times? Also, only EditingTask returns a Cmd, all the others end with ! [])

So, I propose that we break that in four things:

Task: we already have this broken
TaskList: just a list of tasks, nothing else
TaskEntry: something that will become a task
Control: tasks visibility for the app

But wait a minute, what does this TaskEntry has? An id and a description? Hmm it looks like a task! So we can actually simplify our code by reusing the Task type, which will be appended to the TaskList later, then we can get rid of "field" and "uid".

So this is our final models:

This will help us to break our Msgs and Updates

Splitting the Msg

Splitting the Model was very straightforward, likewise, we can break our Msg, from this:

To this:

So, there are a few things to explain here. Notice how we created a new type that holds the msg for each one of our 4 things.

This will allow us, in the view, to say to where in the model we want to send that msg to. At the same time, a single Msg can change multiple parts of our model, for example, when you Add a task, the TaskEntry is appended to the TaskList, but when this Msg happens, the TaskEntry should also erase itself, so the user can type a new task.

Note that the MsgForTask also receives an Int, that's because we need to tell what is the id of the task we are trying to send a Msg.

Splitting the Update

The update is perhaps the part of the code that holds most logic, so I'll just show the TaskList update function, which is the bigger one. You can check out the other updates on the final app code here and here.

So, this update has actually two jobs: handling Msgs specifically for TaskList and directing the Msgs for each task based on its id. Notice how we call "UpdateTask.updateTask msg task", the logic for changing the insides of a Task is no longer here, it's inside the UpdateTask module.

In the update function, the function decides wether it should act on the list, or on a specific item, based on the MsgFor type. It doesn't care about the other Msgs (MsgForControl for example), so it just returns the TaskList as is for them.

This allow us to compose our Update functions like this:

So, when any Msg comes, we pass it through all of our Update functions, to reach our final model.

I showed how can we split the TodoMVC (I won't show how to split the Views because there is almost no changes there, only separating files really), but how do we organize our folders structure?

I achieved two solutions:

1 — Structure with Technical focus

The idea here is having the logic for your modules organizing according to their what they technically are, so basically this:

In each one of those folders have a Task.elm, TaskList.elm and a Control.elm.

Also, in each one we have a file called Main.elm, which combines the other files, e.g. the Update/Main.elm is a combination of all other Updates in the project, the Model/Main.elm is a combination of all other models in the project, and so on.

Then, in our root main function, we just need to use them.

Checkout the code for this structure here.

2 — Structure with Domain focus

This idea is basically a transposed matrix of the first, instead on focusing on the technical aspect, we will focus on our domain:

Inside each one of those folders (including TodoApp), we have a Model.elm, a Msg.elm, an Update.elm, and a Views folder. The TodoApp/Model.elm is a combination of all other models, the TodoApp/Update.elm combines the other updates, and so on.

One argument in favor of this approach is that you can look to the code and discover right away what the app is about, instead of discovering what architecture it uses (we know it will always be The Elm Architecture anyway).

I've also seen this being called as fractal by André Staltz on his blogpost about Unidirectional User Interface Architectures.

A unidirectional architecture is said to be fractal if subcomponents are structured in the same way as the whole is.

So each folder is like a little Elm app itself.

Checkout the code for this structure here.

Conclusion

Even though the Elm language and The Elm Architecture are awesome, we still need to break our code so it can scale a be a full-grown app. Even great languages can produce messy code when in the wrong hands (or timeframe?).

Specially that now, more than ever, you can refactor ALL the things, one, two, a hundred times, without fear, because the compiler is there for you.

This was just my personal ideas on how to achieve that, and I'd love some feedbacks on how can I improve them.

How do you structure your Elm app?