Module list should be consistent about ex_doc

[josevalim]

Hey @alexrp, that's a very good point.

For Elixir, I would be more inclined to go with the second option. I think listing all modules by full name would increase the size of the list and probably hurt discoverability because you would get too much noise.

On the other hand, for other projects (that are not Elixir), the nesting will probably be unnecessary since you would likely have just one root module.

That said, maybe we should go with 1) because it would at least be consistent across the board.

/cc @rafaelfranca

[jwarwick]

Anyone have further thoughts on this issue? I made a feature branch that lists the whole module name (without nesting) to see what it would look like: jwarwick/ex_doc@87b6e1f

For the Elixir source, it looks okay. The Mix.Tasks.* list gets a bit long though.

[josevalim]

It is your call @jwarwick :)

[jwarwick]

Ha! Not sure I'm up for this level of pressure 😰

I'll stare at a bit more, maybe try indenting the children and see if that helps with the noise.

[josevalim]

Hahaha, don't worry @jwarwick! we can always experiment with some approaches too and then rollback if we are not comfortable with it. Just to have something to compare, I have pushed elixir docs using your changes to the master docs, so people can compare the two versions directly:

http://elixir-lang.org/docs/master/ (new)
http://elixir-lang.org/docs/stable/ (old)

I will send an e-mail to the mailing list too and get some feedback!

[josevalim]

And for what is worthy, I prefer the new format, much easier to discover and see which modules are available. There is some noise but it is easy to scroll through it. 😄

[josevalim]

@jwarwick I think we should go ahead and merge your changes. Would you please send a pull request or merge into master? :)