Add pagination to requests

[3nt3]

When you query /users for example, you get all of the users in an array. That's cool for simplicity but when there are more users, this will probably result in unbearable loading times along with way too many items in the front end.

Proposal: Add pagination (for example: ?start=somenumber and ?end=anothernumber or ?start=somenumber and ?n=someothernumber)

[durek1337]

I prefer the page number and the entries per page 😄 The backend should also return the amount of all entries found for pagination. The possibility of searching a user by its properties would also be nice at this place.

[durek1337]

I would like to push this thread. This issue is the only one I see which interrupts our scalability. Please work on this issue with highest priority. Maybe we should also consider to filter inactive accounts for the requests by filtering with the SQL-Request.

Summary

• Pagination to requests
• Pagination for the users on the admin page (also with searching users by its properties)
• Filter inactive accounts in the request-page