-
Notifications
You must be signed in to change notification settings - Fork 14
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
Implement Rate limit checking #43
Comments
We can expose the headers (or at least some headers field) within headers <- httr::headers(request_results)
output <- httr::content(request_results)
attr(output, "headers") <- headers
return(output) |
I was thinking that too.I will built that into the refactoring in #31. We then have a preliminary wiki page which can explain how to paginate accessing the attribute and we built a robust solution later. I think this needs a bit more time to come up with a good solution |
rate limits are now returned in the attribute "headers" of the output |
still need a function to explicitly check the rate limit |
No endpoint exists to check the ratelimit. ratelimit is only returned in the header of a get request. |
To implement pagination (#41), we need to keep track of rate limits
The text was updated successfully, but these errors were encountered: