better api error handling on the cli
See original GitHub issueIf any of the API calls throw 504 etc or a non-JSON response, the CLI errors out saying
FATA[0031] apply failed: invalid character '<' looking for beginning of value
which is not really helpful for a user.
For all unknown API-errors, the CLI should print out the response code and body.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Unclear Error Handling for Status-Only API Response #4734
I've hit an issue where a gh api call returns a 409 and no body (or a blank body), and gh api doesn't...
Read more >Best Practices for Node.js Error-handling - Toptal
This article will introduce you to error-handling in Node.js and ... errors include “out of memory,” “an invalid input for an API endpoint,”...
Read more >Better Error Handling In NodeJS With Error Classes
This article is for JavaScript and NodeJS developers who want to improve error-handling in their applications.
Read more >Error handling of CLI applications in Golang
When developing some CLI applications in Go, I always consider the main.go file as "the input and output port of my application." Why...
Read more >Learn Bash error handling by example | Enable Sysadmin
There's no better way to learn how to handle errors in your Bash scripts than to see it done.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@dotslash21 we have created a wiki describing everything you need to know about Hasura & Hacktoberfest: https://github.com/hasura/graphql-engine/wiki/Hacktoberfest-2019-🎉 🙂
I will take it @marionschleifer