summaryrefslogtreecommitdiffstats
path: root/apps/settings/src
diff options
context:
space:
mode:
authorVincent Petry <vincent@nextcloud.com>2021-02-02 18:02:03 +0100
committerVincent Petry <vincent@nextcloud.com>2021-02-04 08:52:51 +0100
commit49568e2a31fcfd75e88272c74345cd19766d04a1 (patch)
tree471d6d4d3f2d8d95d3ea8a1fe6c558b951e7af2d /apps/settings/src
parentdf9ce19a6b0db6bbe74c12b184ac798787344cfa (diff)
downloadnextcloud-server-49568e2a31fcfd75e88272c74345cd19766d04a1.tar.gz
nextcloud-server-49568e2a31fcfd75e88272c74345cd19766d04a1.zip
Make user list pagination more tolerant
In case the server returns more results than expected by the limit, it is now still interpreted as there being more results to query. This situation can happen when there are multiple user backends in place. Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Diffstat (limited to 'apps/settings/src')
-rw-r--r--apps/settings/src/store/users.js4
1 files changed, 2 insertions, 2 deletions
diff --git a/apps/settings/src/store/users.js b/apps/settings/src/store/users.js
index 41f2f4e4e8d..7877c3f3a52 100644
--- a/apps/settings/src/store/users.js
+++ b/apps/settings/src/store/users.js
@@ -220,7 +220,7 @@ const actions = {
.then((response) => {
if (Object.keys(response.data.ocs.data.users).length > 0) {
context.commit('appendUsers', response.data.ocs.data.users)
- return Object.keys(response.data.ocs.data.users).length === limit
+ return Object.keys(response.data.ocs.data.users).length >= limit
}
return false
})
@@ -237,7 +237,7 @@ const actions = {
.then((response) => {
if (Object.keys(response.data.ocs.data.users).length > 0) {
context.commit('appendUsers', response.data.ocs.data.users)
- return Object.keys(response.data.ocs.data.users).length === limit
+ return Object.keys(response.data.ocs.data.users).length >= limit
}
return false
})