Repository navigation
Special error message for rate-limit responses - #238
Open
Toastbrot236 wants to merge 3 commits into
Open
Toastbrot236 wants to merge 3 commits into
Toastbrot236 wants to merge 3 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR for the legacy website where the error message for the login and register requests, aswell as the one returned by
ApiRequestCreator.handleRequestError(), is overwritten manually with a more user-friendly message telling the user they've been rate-limited. The message also discourages the user from spamming requests, and tells them to try again later. The message doesn't include the time given by theRetry-Afterheader yet, but this should be enough for now (also, Refresh currently only returns this header on the first rate-limit anyway).