Get Next and Previous should not use cursors #623
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://developers.facebook.com/docs/graph-api/results/
===
For example: If my cursor has total 4 items (default limit is 25)
So I need to make one request to get the cursor with 4 items. The current code getNext() will always return a URL and
fetchAfter() will execute one more request and return an empty data. So, we need to make 2 requests to get for only 4 items.
So if $content['paging']['next'] is empty, we should return null and do not need to make more requests