Sorry, I don’t follow what you’re saying here.
The stock Elixir tool for chaining multiple operations and return on first error is with. I prefer to use that instead of some custom library mechanism.
Yes, and I’m not returning it from vanilla Elixir. Multi OTOH requires you to return something in each step. It could be nil, I guess, but IME that’s confusing, because we end up with named things which are always nil.
If there’s an error inserting the user, this code will commit and return {:ok, {:error, changeset}}. This is how transaction + fun work, and it’s specifically what transact changes (by wrapping transaction).
Furthermore, the case version is noisy even in such a simple example, and it becomes progressively worse when you want to chain multiple operations, exiting early on some (but not all) of them. IIRC, this is precisely why with was introduced to the language.
Sorry, no idea what this means. What is being rewritten?
I agree. Given its API, multi pushes folks to uncritically return non-actionable errors, in the places where they should raise. I’ve seen way too much of such code.
