You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aside from difficulties in implementing a custom FileAdmin (documentation is a bit lacking), one thought I had while reviewing the code of both existing FileAdmin modules was "Why can't I find any sort of pagination?". If I were to have thousands of hosted images, given the current structure of FileAdmin all images would be requested from the api in one go and rendered with pagination on the front-end. This seems terribly inefficient (and costly in terms of API rate-limits).
Is it possible to implement proper ajax pagination to FileAdmin? I saw in the original pull request #1154 that implemented the s3 FileAdmin there was a comment about implementing pagination (link), but it never seemed to make it into the FileAdmin.
The text was updated successfully, but these errors were encountered:
Aside from difficulties in implementing a custom
FileAdmin
(documentation is a bit lacking), one thought I had while reviewing the code of both existingFileAdmin
modules was "Why can't I find any sort of pagination?". If I were to have thousands of hosted images, given the current structure ofFileAdmin
all images would be requested from the api in one go and rendered with pagination on the front-end. This seems terribly inefficient (and costly in terms of API rate-limits).Is it possible to implement proper ajax pagination to
FileAdmin
? I saw in the original pull request #1154 that implemented the s3 FileAdmin there was a comment about implementing pagination (link), but it never seemed to make it into the FileAdmin.The text was updated successfully, but these errors were encountered: