Missing nextpageRef in results for branch wip-api-adjustments

[flaviotordini]

nextpageRef is never present in the data returned by ytsr so pagination is impossible.

[TimeForANinja]

the pagination responses don't include the basic meta information therefor pagination is currently only implemented internally linked to the limit option

[flaviotordini]

Btw, I found that setting the limit above 20 always causes an error: The "listener" argument must be of type Function. Received type object

[TimeForANinja]

May i ask which version & branch you run and as well as your node.js version?

[patrickkfkan]

Hello,

Are there any plans to include nextPageTokens in the results so we can continue a previous search? Thanks.

-Patrick

[TimeForANinja]

it should be fast to add a continuation property would work a bit different from the nextPageToken thou...

[patrickkfkan]

I see you've made some changes to support continuation in the wip branch (also for ytpl). That was quick~ Thanks a lot!

So if we need to continue a previous search, we would use 'pages' instead of 'limit', and each 'page' will have 100 results. Is that correct?

[TimeForANinja]

as mentioned - was quick to add ytpl should return 100 results ytsr should return 22 results i can't enforce this thou, so it might vary

i wanted to add pages for a while now, since it is a way more efficient way (talking request count and therefor ratelimits)

disabled continuation for limit since continuation works in whole pages - so doing sth like ytpl(id, {limit: 25}) followed by a continuation call would result in one page being fetched, item 26-100 spliced since it's over the limit and item 101-200 being fetched by the continuation