Paginator does not work correctly

[studna]

I'm trying to paginate followers, but I can't figure it out because of response structure (list of followers is under 'users' key). Is there any easy solution to solve this?

Many thanks.

[akadlec]

Twitter does not use pagination. You have to specify start point and all tweets are loaded automatically.

[studna]

When I try to list followers via IPub\Twitter\ApiCall::get() it returns IPub\Twitter\Paginator and there is no way to get correct data from it. Checkout the API method I mentioned and you'll quickly see, what my problem is.

[akadlec]

I've got your point. Ok now the extension can support only statuses, because they are not under subarray. What i can do is to create some "map" for other type of lists or not return Paginator for this diiferent lists.

[jirinapravnik]

Same problem here with users/search endpoint. IMHO should be better leave Paginator only for statuses or remove full Paginator...

[studna]

@jirinapravnik I have a solution (two paginators). It's little uggly (extending the extension), but it works. https://gist.github.com/studna/fe7f54f28b5dd58d38030a2a46a25972

[jirinapravnik]

@akadlec what solutions would you like to see? i would prepare PR for it

[akadlec]

Hmm...two options, full refactoring of paginating functions or use paginator on some endpoints