-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose internal debug functionality #764
Comments
This is specially useful for the CLI. A
Present error information is not too useful for the end CLI user.
|
Its Something like the Fetch API doesn't throws error on other error codes except network failure. Something like below might help you, if you are using Fetch API. const response: Response = await fetch(hostname);
console.log(response.status); // Note: This status actually contains the error codes
// like 401,403 as well I can create a PR if you want, I think it can be solved by using this |
Any update over this @jdalrymple ? |
Not yet, focusing on fixing up the things already in the PR stage |
Really should do this one 🤦 |
Exposing the response in the Error's cause property in #2258 |
Description
Not sure what the best way to do this would be, but having a way to view some of the internal process would be very useful in debugging. passing a debug property that had things like the raw requests and more.
Proposal
Open to ideas here!
The text was updated successfully, but these errors were encountered: