Fix for the pagination on watchlist pages#20
Merged
MatteoCampinoti94 merged 7 commits intoFurryCoders:mainfrom Sep 27, 2025
Merged
Fix for the pagination on watchlist pages#20MatteoCampinoti94 merged 7 commits intoFurryCoders:mainfrom
MatteoCampinoti94 merged 7 commits intoFurryCoders:mainfrom
Conversation
Collaborator
|
Thanks for letting me know and for the PR! There is no need to do all those checks for the page, the library is actually designed to fail when it encounters something that unexpected, like a next-page value that is not an integer, so that whoever uses can see something is wrong instead of receiving a seemingly valid value. |
MatteoCampinoti94
approved these changes
Sep 27, 2025
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
2 participants
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.
The last site update changed the pagination on the watchlist pages.
Because of this watchlist_to and watchlist_by always immediately return None for the next page.
This should be a possible fix for it.