Slight tangent, but I think that much of the material online (both docs and tutorials) suggests that Phoenix forms is the “right” way. Of course you can structure your forms however you wish, but I think coupling is implicitly encouraged. You certainly give up a lot of wonderful developer ux when you decouple them from the DB, and it adds friction to the correct choice. I certainly doubted myself whenever I strayed from them in the early days.
Could this be an area like Phoenix pre-Contexts, where the encouraged behaviour is actually something on an anti-pattern? Perhaps much like the generators, Phoenix Forms need a disclaimer: “These are great for simple use care X, but not so great for more complicated use case Y.”
