New: (Cardigann) Paging Support - v9 #1479
Draft
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.
Database Migration
NO
Description
{{ .Query.Page }}
and{{ .PageSize }}
in yml, thispage
is auto calculated based on the offset and limit passed to Prowlarr and the page size defined in the YMLThis should handle all paging scenarios
Examples
Indexer Page Size: 100 - User Search: Offset 100, Limit 100 - We should get page 2
Indexer Page Size: 100 - User Search: Offset 50, Limit 100 - We should pull page 1 and 2 and return correct items
Indexer Page Size: 100 - User Search: Offset 0, Limit 200 - We should pull page 1 and 2 and return all
Indexer Page Size: 100 - User Search: Offset 120, Limit 40 - We should get page 2 and return the correct results
Indexer Page Size 20 - User Search: Offset 40, Limit 100 - We should get and return pages 3,4,5,6,7
Todos
Fixes #379
Fixes #1470