fix: handle 404 errors, fix error handling for client.resolve #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a couple things related to error handling:
W3NameClient::resolve
now actually checks the status code of the API response and returns errorsAPIError
now includes the HTTP status codeprocess::exit
instead of panickingpublish
command now only falls back to creating an initial revision if the request for the current revision returns 404. Other errors are treated as failures and printed. Closes add better error handling for publish command #4