Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support pagination on API responses #77

Open
dmckernanacv opened this issue Apr 11, 2022 · 0 comments
Open

Support pagination on API responses #77

dmckernanacv opened this issue Apr 11, 2022 · 0 comments

Comments

@dmckernanacv
Copy link

URLs which return list-based results do not do any pagination, leading to out-of-memory issues for websites with a grand audit history.

Pagination should be implemented on all API routes which return a list of items, with a sensible default (to gracefully integrate with the existing Backstage UI plugin)

My use case:
We automate lighthouse audits for our website 3 times a day, (as we deploy multiple times per day) however, the array has become so large that the lighthouse audit service pod is crashing because it doesn't have enough memory to handle the response from /v1/audits/:auditId/website

I propose pagination is added to every API route which returns an array with a default limit of 25 items per page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant