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

fix: better error for invalid client id or client secret #84

Merged
merged 2 commits into from
Oct 19, 2022
Merged

Conversation

bobbyg603
Copy link
Member

The 401 case is a tricky one, you can have a valid token, but if it can't access the specific resource a 401 error happens late in the request chain. We want to catch 401 errors and give at least some sort of helpful error message.

@bobbyg603 bobbyg603 merged commit 16b349a into main Oct 19, 2022
@bobbyg603 bobbyg603 deleted the 401 branch October 19, 2022 15:13
bobbyg603 pushed a commit that referenced this pull request Oct 19, 2022
## [2.1.1](v2.1.0...v2.1.1) (2022-10-19)

### Bug Fixes

* better error for invalid client id or client secret ([#84](#84)) ([16b349a](16b349a))
@bobbyg603
Copy link
Member Author

🎉 This PR is included in version 2.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants