API change - Sonarr Torznab pagesize limits

[Taloth]

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! We accept bounties via Bountysource.

[ghost]

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]

Awesome, good to hear.

[cybercorey]

Hey, what does running it on the .net core mean for us Linux users running mono?

[JigSawFr]

@cybercorey With .net core, mono will be no longer used.

[cybercorey]

Will we still be able to run this on linux?

[JigSawFr]

Yes of course !

[mrjackyliang]

I tried this, it doesn't work.

[bonfire62]

Any update on this?

[mrjackyliang]

The offset and limit works for me now.

[B1773rm4n]

What is happening here?