Elixir

Notes to self about the unexpected quirks of the otherwise excellent PhoenixTest library.

Placing schemas inside contexts makes it difficult to distinguish between data and actions. Let's fix that.

In a Phoenix context we frequently need to create and update resources, using changesets. Each operation requires a function to get the changeset, and a function to perform the operation.

If the operation in question is "create", the standard approach is to name the changeset function create_changeset, but that's just confusing; am I getting a changeset for the "create" operation, or am I creating a generic changeset?

I prefer the following conventions.