Currently the /users API being used in the members page is provided with a size limit of 100 and It will break the page once we have more than 100 users.
Proposed Solution
Overview:
By using the paginated /users API. show the members and non-members in sets of 100 for every button click of Previous or Next.
Client-Side Pagination:
Only load and display a reasonable number of results per page. When the dataset is very large, avoiding loading all the data at once. Instead, load data in chunks, and allow the user to navigate through different pages.
Example: The pagination of tasks on status site
https://api.realdevsquad.com/tasks?dev=true&size=5&next=nPpNHFs3jTbApQpd07qQ
Problem Statement
Currently the
/usersAPI being used in the members page is provided with a size limit of 100 and It will break the page once we have more than 100 users.Proposed Solution
Overview: By using the paginated /users API. show the members and non-members in sets of 100 for every button click of Previous or Next.
Client-Side Pagination: Only load and display a reasonable number of results per page. When the dataset is very large, avoiding loading all the data at once. Instead, load data in chunks, and allow the user to navigate through different pages. Example: The pagination of tasks on status site https://api.realdevsquad.com/tasks?dev=true&size=5&next=nPpNHFs3jTbApQpd07qQ