-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pagination in search endpoint #92
Comments
Is this "search/byterm" you are speaking of? |
Indeed. I am assuming it would also make sense for a few other endpoints
like the "trending" one.
…On Tue, 28 Feb 2023 at 18:15, Dave Jones ***@***.***> wrote:
Is this "search/byterm" you are speaking of?
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABP4W3QNYKITU37AY6DZCXDWZYXBLANCNFSM6AAAAAAUAHR5IM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I agree. Currently I don't see a way that I can get a paginated response from the API |
In testing |
There is a 60 item limit on search. I experience the same behavior when searching for popular terms. There is sadly no way to increase the maximum amount as well. Although this is more of a "hot fix". | My use-case is showing users trending podcasts for a given category as well as "infinite scrolling" for both trending and search. I've read multiple times that constraint developer time is a problem for the pagination feature. Given that, I'd be willing to spend some time to implement this. I feel like this would enhance products based on the podcastindex.org API immensely! You can contact me using my public GitHub E-Mail! |
For the search endpoint, I would love a pagination option.
Right now to create eg. 10 pages of results, I have to request 100 results. It would be nice if I could add a param "offset" or something like that.
Hopefully it should be relatively easy to do in your PHP/SQL
$offset = intval($_REQUEST["offset"]) ? intval($_REQUEST["offset"]) : 0;
SELECT
blah
FROM
search
LIMIT ".$offset.",".$max."
Done deal! (yes, I know it's likely not as simple as that) 😄
The text was updated successfully, but these errors were encountered: