Skip to content

feat: correctly handle 429 status from Discord #28

Description

@JerryImMouse

Problem / motivation
Currently Im just silently pass the 429 to the API caller.

Proposed solution
We should read the headers which Discord provides to address its rate limiting buckets and remaining requests. This involves some boilerplate to implement, but have to be done. It can become a huge problem later

Alternatives considered
I can't see any alternatives to do this.
According to Discord Docs the upper way is the only correct way of doing this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions