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

Allow sending requests but not wait for ratelimits (error instead) #45

Closed
TAG-Epic opened this issue Jun 10, 2022 · 1 comment
Closed
Labels
scope/nextcore.http Any changes to the nextcore.http namespace type/feature A feature addition

Comments

@TAG-Epic
Copy link
Member

Currently you have to wait for a ratelimiter, there is no option to just fail if the bucket is ratelimited.

Maybe make it so you can change this for global and scoped independently?

@TAG-Epic TAG-Epic added enhancement type/feature A feature addition scope/nextcore.http Any changes to the nextcore.http namespace and removed enhancement labels Jun 27, 2022
@TAG-Epic
Copy link
Member Author

Fixed in #131

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/nextcore.http Any changes to the nextcore.http namespace type/feature A feature addition
Projects
Status: Pending release
Development

No branches or pull requests

1 participant