Read `project.name` if `project.package.name` is not available.

[Qqwy]

As was discussed on the elixir-lang-core mailing list (https://groups.google.com/forum/#!topic/elixir-lang-core/kve1an2xwus), the :name field was extracted from mix.exs' project.package.name to just project.name so that multiple different libraries would be able to read it.

This is a convention that other libraries such as ExDoc already follow. Having both a project.name and a project.package.name might be confusing and is in (nearly?) all cases superfluous.

Proper behaviour, as @josevalim and @ericmj confirmed, is that project.name should be read, with project.package.name overriding this setting. Or, in other words, project.name should be read iff project.package.name is not available.

[agustif]

Would it be enough to edit hex.publish.ex there are various mentions to:

name = build.meta.name

Would be the best way to create a private function to put the logic to fetch from build.name first, and build.meta.name in case of build.name being empty or not valid?

[ericmj]

The name in project.name is not the same name as in project.package.name. The first is the human readable name of the project in capitalized form, the latter is the name of the package, all in lower case. For example project.name: "Phoenix Framework" and project.package.name: "phoenix".

[Qqwy]

@ericmj Wait! I think this means that some documentation is incomplete somewhere. I am not sure this is something that is part of Mix or Hex (I think the Hex as Mix itself only uses project.name), but we should improve the documentation to clarify this difference.

And if indeed project.package.name should always be a lowercase name, maybe we should constrain it and error or warn when a user enters something that does not follow this rule.

[ericmj]

If there is wrong documentation we should of course fix it, please let us know if you find anything. Hex.pm will validate the package name.

On Tue, 30 May 2017 at 13:35, Qqwy ***@***.***> wrote: @ericmj <https://github.com/ericmj> Wait! I think this means that some documentation is incomplete somewhere. I am not sure this is something that is part of Mix or Hex (I think the Hex as Mix itself only uses project.name), but we should improve the documentation to clarify this difference. And if indeed project.package.name should always be a lowercase name, maybe we should constrain it and error or warn when a user enters something that does not follow this rule. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#364 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATV2kJGQ1uvDeSiIVkKZrC87Gy3A4iCks5r-_8GgaJpZM4NFNG4> .

-- Eric Meadows-Jönsson

[Qqwy]

For posterity:

(01:58:35 PM) qqwy: By the way, the original hex issue can then be reframed; instead of reading project.name if project.package.name is unavailable, we could read project.app instead (as project.package.name is usually based on this anyway.
(01:59:39 PM) ericmj: qqwy: we already do that

So I guess this issue can be considered 'completed' for some definition of completed. 😄