I think it’s rather an edge case especially to make code “shorter” and have a single “helper” module for this. It’s most probably because this code is not a part of a hex package, but a simple and short not documented (private functions have no documentation) part of your codebase. They are short and contains just a few aliases/imports and stuff like that. I would say it would be divided in few modules only if the inside logic would be more complex than what we have right now.
The entire ExampleWeb module logic is just so simple that it can’t compare to the logic of a typical macro. Also I believe it’s easier to maintain such helper in a single file rather than working on multiple files. The current Phoenix version have already impressive structure and does not need a bunch of tiny files just to separate such a simple logic.
