Subjectively I don’t see custom wrappers have any use for me, because:
- We already have
mix help …command if something is not clear. - It’s not good way for copy-paste examples (learning resources, creating similar project etc.)
- They are harder to enhance comparing to simple
bashautocompletion scripts
If I really would need to add something then it would be a simple bash script for autocompletion.
Also since lots of Unix commands supports passing arguments like you do, I would rather ask a phoenix core team if such idea could be merged to phoenix project instead of creating a wrapper.
If we would take a look at phx.new task code then we would see how simple would be a way to add prompts:
https://github.com/phoenixframework/phoenix/blob/4c9737cd1020ddb21cf1a8a714e6dc88317fd843/installer/lib/mix/tasks/phx.new.ex#L120-L130
In this case simple defp parse_opts([]) do … end function clause would do the work.


















