Root task (mix hex) should display help about hex

[jcspencer]

I also think delegating calls from mix hex <command> [arguments...] to mix hex.<command> [arguments...] would be useful for newcomers as well, as everything would be available under the hex command. This would, of course, be backwards compatible with the current tasks (as it's really just calling them).

e.g. mix hex.info -> mix hex info or mix hex.owner add [arguments...] -> mix hex owner add [arguments...]

[josevalim]

I think delegating is confusing. I know the goal is to help on typos and newcomers, but then people write tutorials, some using one syntax, some use others, and that ends up causing a lot of confusion. Plus, it would only work with hex, and not other tasks, causing even more confusion.

We are going to support mix help --search hex on Elixir v1.0, mix hex could simply invoke it.

[jcspencer]

@josevalim Now that I think about it, that would get very confusing in many ways 😕

Maybe we could output something like this for mix hex:

Hex is a package manager for the Erlang ecosystem. This is
a basic help message containing pointers to more information.

Usage:
  mix hex (this command)
  mix hex.command [arguments...] [options...]

Tasks:
>output from mix help --search hex<

Further information can be found here: https://hex.pm/docs/tasks

[ericmj]

I don't like the idea of having a task solely for documentation. We could isntead rename hex.info to hex and delegate to elixir-lang/elixir#2807.

[jcspencer]

Would something like this work? https://gist.github.com/JamesS237/e3ad837a8e052443f645

[ericmj]

Looks good

[jcspencer]

What should we do for Elixir versions older than v1.1.0? (regarding mix help --search PATTERN support)

[ericmj]

We don't call it for pre 1.1.0

[jcspencer]

Should we simply call Mix.Task.run("help", ["--search", "hex."]) in the task if the version is >v1.1.0?

[jcspencer]

Closed in #88