handle ApiKeyValidateRateLimitedException #28
Merged
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.
After PR
Introduces
ApiKeyValidateRateLimitedExceptionerror for rate limiting end-user api keys. This includes the fieldswaitSeconds(decimal of seconds until a key/user/org is no longer rate limited),userFacingError,errorCode(alwaysrate_limit_exceededfor this case).Example use once
ApiKeyValidateRateLimitedExceptionis passed through the node repo:Tests
Using yalc and publishing to a local repo of the
nodelibrary, I verified the expected behavior in an example app that validates api keys