API change - Sonarr Torznab pagesize limits

Taloth commented 8 years ago

I've made a commit for Sonarr develop that will read the 'limits' caps attribute to determine the page size instead of keeping it hardcoded to the 100 newznab default. <limits max="100" default="100"/>

You may want to add that element in your t=caps responses and adjust the value as appropriate for each tracker. That way sonarr will know how big the page is supposed to be, and fetch multiple pages. Obviously only works if jackett appropriately handles the &offset=xx&limit=xx queryparam.

A bit a continuation of our chat in #27.

Can you guys look into it, and potentially test it on the develop version of Sonarr?

Here's the commit please note that max and default should be the same value.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30956740-api-change-sonarr-torznab-pagesize-limits?utm_campaign=plugin&utm_content=tracker%2F25207257&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F25207257&utm_medium=issues&utm_source=github).

ghost commented 8 years ago

Thanks for the heads up @Taloth We have started a complete rewrite of Jackett based on .NET Core. We'll definitely be supporting this along with paging in the rewrite.

Taloth commented 8 years ago

Awesome, good to hear.