Skip to content
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

Add more verbose error messaging #125

Open
zemberdotnet opened this issue Oct 24, 2022 · 0 comments
Open

Add more verbose error messaging #125

zemberdotnet opened this issue Oct 24, 2022 · 0 comments

Comments

@zemberdotnet
Copy link
Member

Currently, the client tries to unmarshal the response into the declared type. When there is an error like Unauthorized this ends up failing with a a message like json.Unmarshal parse error U at line 1:1, which isn't very helpful to the end user.

Upon failing to decode a response, we should fall back to a more general conversion and use that in our error reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant