clones/friendica
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Implement correct behavior for min_id in boundary pagination

Browse Source 
- The previous behavior of since_id systematically showed the most recent results
This commit is contained in:
Hypolite Petovan
2020-10-12 23:45:02 -04:00
parent e0a6b90316
commit 4427876c05
10 changed files with 101 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/Module/Api/Twitter/ContactEndpoint.php
View File

@@ -155,15 +155,24 @@ abstract class ContactEndpoint extends BaseApi
$total_count = (int)DBA::count('contact', $condition);
$params = ['limit' => $count, 'order' => ['id' => 'ASC']];
if ($cursor !== -1) {
if ($cursor > 0) {
$condition = DBA::mergeConditions($condition, ['`id` > ?', $cursor]);
} else {
$condition = DBA::mergeConditions($condition, ['`id` < ?', -$cursor]);
// Previous page case: we want the items closest to cursor but for that we need to reverse the query order
$params['order']['id'] = 'DESC';
}
}
$contacts = Contact::selectToArray(['id'], $condition, ['limit' => $count, 'order' => ['id']]);
$contacts = Contact::selectToArray(['id'], $condition, $params);
// Previous page case: once we get the relevant items closest to cursor, we need to restore the expected display order
if ($cursor !== -1 && $cursor <= 0) {
$contacts = array_reverse($contacts);
}
// Contains user-specific contact ids
$ids = array_column($contacts, 'id');