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.
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/websiteI propose pagination is added to every API route which returns an array with a default limit of 25 items per page.