I love the explicit parts of Phoenix, like endpoint.ex listing out all the plugs that run before the router.

I remove web.ex from Phoenix projects, as it hides the source of the functions that are imported.

My ideal Phoenix wouldn’t support convention based selection of the view module from the controller module name for the sake of saving a single function parameter.

It’s great that Phoenix lets me use it in a way that is explicit and free of magic

Less macros, more functions instead. Most irritating examples:

• my_app_web.ex which use __using__/1 magic for including different set of modules in different parts of the application, especially when most of them do not need such at all, and should be left up to the user whether they want to include some of the headers
• Phoenix.Channel.intercept/1, is there any good reason why this is macro rather than just module attribute?
• Phoenix.ConnTest.{method} macros, what is the advantage over plain functions?

Also I would change naming from MyAppWeb.ActionController to MyAppWeb.Controllers.Action (the same for views, channels, sockets, etc.) so it will suit general naming convention within Elixir.

I would prefer MyAppWeb.Action.Controller, MyWebApp.Action.View etc so modules are grouped by the business domain rather than the “kind” of module.