search

elm / error-message-catalog

A catalog of broken Elm programs / data to improve error messages
BSD 3-Clause "New" or "Revised" License
173 stars 17 forks source link

Package name not matching github repo name produces misleading error #300

Open tad-lispy opened 5 years ago

tad-lispy commented 5 years ago

Quick Summary:

While publishing a package I made a mistake in the name field so it was not matching the address on GitHub. The error was:

  ✗ Version 1.0.0 is not tagged on GitHub!

-- NO TAG ----------------------------------------------------------------------

Packages must be tagged in git, but I cannot find a 1.0.0 tag.

These tags make it possible to find this specific version on GitHub.
To tag the most recent commit and push it to GitHub, run this:

   git tag -a 1.0.0 -m "new release"
   git push origin 1.0.0

The -m flag is for a helpful message. Try to make it more informative!

Which is very misleading.

SSCCE

N/A

Additional Details

I would suggest a message like that:

  ✗ No repository by name tad-lispy/springs on github.com.

-- NO REPOSITORY -----------------------------------------------------------------

I was looking for https://github.com/tad-lispy/springs.git, but it's not there! Packages must be published to GitHub before they can be published to packages.elm-lang.org.

Maybe there is a mistake in the elm.json file? Check out the name field.