-
Notifications
You must be signed in to change notification settings - Fork 201
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
Use TWIT_paginate_cursor in more places #552
Conversation
@llrs I'm having a hard time getting collections to work, because their APIs are so different. What do you think about just getting rid of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding more API references I missed.
With this PR I finally I understood how useful TWIT_paginate_cursor is.
Most comments are to increase the number of results returned on each page to minimize the number of requests.
About lookup_collections()
and get_collections()
, I agree to deprecate. Twitter itself did the same, so I don't see any value on keeping them: https://developer.twitter.com/en/docs/twitter-for-websites/timelines/guides/collection
Co-authored-by: Lluís <llrs@users.noreply.github.com>
Conflicts: NEWS.md
Since it can return at most 100 users.
Replacing hand-rolled pagination code. This increases consistency and is one step towards #510.