fix: torznab paging - #42
Merged
Merged
Conversation
Exclusion and multi-file filters now run before the reported total is computed and before offset/limit are applied, so pages fill correctly and clients no longer page past the end. Scoring runs on the full filtered set, so the preferred release no longer depends on which page it lands on.
render_feed accepted offset and total but never emitted them, leaving Sonarr/Radarr without the <newznab:response> element they use to drive paging.
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.
Torznab items were being filtered after offset/limit was applied which means page sizes were often shorter than they should be.