[020.5] Elm Weekly Drip #20 and Exercise: Edit Users

Elm Weekly Drip #20 and Exercise: Edit Users
[08.27.2016]

Link day is here! Also, an exercise to add the ability to edit users. As for
the links, you'll: figure out what to do; convince a friend to try Elm; discover
that Evan handles 'blocking' problems with humor; port imperative loops; learn
what not to say; and see lots about structuring large apps.

Folkert de Vries wrote up a pretty fun post on
translating imperative algorithms to a functional language. I had never heard
of paramorphisms before. I still don't have a heuristic for why I want them,
but it was a fun read none the less.

Here's a reddit thread where Evan pipes in on his concerns with the use of the
word components in discussions of Elm. Money quote: overzealous naming and
conceptualizing can very easily lead people to bad results.

OK that's kind of linkbaity of me, but bear with me. This thread begins as a
discussion of how to structure large Elm apps, which of course comes up
constantly (way more than it should). It devolves a bit in the middle, but
there are a lot of juicy nuggets worth reading if you care about these things.

Exercise

This week we built a basic CRUD application in an elm-mdl single-page-app atop
our Phoenix API but we can't actually edit users yet. You should be able to add
an edit page that lets you click on a user, edit them, and then push those
changes back to the Phoenix API. When the user is updated successfully, it
should redirect you to that user's show page. Next week I'll show you how I'd
handle it. Thanks!

sign up for full access

Meet your expert

I've been building web-based software for businesses for over 18 years. In the last four years I realized that functional programming was in fact amazing, and have been pretty eager since then to help people build software better.