-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(rest)!: allow passing tokens per request #10682
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10682 +/- ##
==========================================
+ Coverage 37.96% 37.99% +0.02%
==========================================
Files 239 239
Lines 14877 14889 +12
Branches 1377 1385 +8
==========================================
+ Hits 5648 5657 +9
- Misses 9218 9221 +3
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
BREAKING CHANGE: `RequestData.authPrefix` has been removed in favor of `RequestData.auth.prefix`
5453148
to
1bf3ba4
Compare
Co-authored-by: Jiralite <33201955+Jiralite@users.noreply.github.com>
BREAKING CHANGE:
RequestData.authPrefix
has been removed in favor ofRequestData.auth.prefix
Please describe the changes this PR makes and why it should be merged:
This allows passing a token when making a request (mostly useful for OAuth endpoints) and moves the token prefix into the same object as it didn't make sense having it separate.
This separates handlers based on the token used to isolate (non-global) ratelimits. There is a chance that ratelimits are hit if a bucket spans tokens. It does respect bucket hashes, so after the first request with each token they will be bucketed together.
Fixes DJS-41
Status and versioning classification: