feat: add RateLimited gateway event #1334
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Jiralite
previously approved these changes
Aug 15, 2025
vladfrangu
requested changes
Aug 15, 2025
| /** | ||
| * @see {@link https://discord.com/developers/docs/events/gateway-events#rate-limited} | ||
| */ | ||
| export type GatewayRateLimitedDispatch< |
There was a problem hiding this comment.
This should be a union of concretes, not require users to pass in the op code they want imo. That said, how you'd present this is...gonna be fun
There was a problem hiding this comment.
I made it as close as docs as possible.
Additionally, the type parameter has a default (all the valid opcodes, which is only one anyways), if that's your concern
There was a problem hiding this comment.
We should still export aliased types for speed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please describe the changes this PR makes and why it should be merged:
If applicable, please reference Discord API Docs PRs or commits that influenced this PR: