Closed tsloughter closed 2 years ago
This is sort of fixed in master now as part of #272 ... but there's a part that's still "meh".
Currently (master) this will now result in :
===> Failed to publish docs for truecoat - 0.4.660 : Page not found
We could check to see if we get "Page not found" message back from hex, and if so suggest a few things :
===> Failed to publish docs for truecoat - 0.4.660 : the 0.4.660 package could not be found, be sure your publishing docs for the same version as the package you intend to the docs to go along with.
Of course, we're making an assumption there. Thoughts?
Edit:
What would be better is to send a PR up to hexpm to return a better error message IMO.
Failed to publish docs for truecoat - 0.4.660 : the truecoat package at version 0.4.6660 could not be found
would likely contain all required information to double-check things, without being misleading if the issue is say, Hex being down.
Publishing docs for a version of a package that doesn't exist results in a crash instead of an error message: