Currently, we're using Gitea's API for sorting and pagination handling when fetching apps on the dashboard.
The challenge here is that Gitea's API does not support sorting by updatedBy or description, and it also cannot use "excluding keywords" like -datamodels. In order to only show the actual apps, not including data models, we have to filter on the client side, after having received all repos.
This leads to bugs like the one shown below, where we fetch a page with 5 rows, filter out 1, and the user ends up with 4 rows being displayed, even though the page size is set to 5:
Potential solutions:
Move all sorting and pagination logic to the Designer backend
Make our backend wrapper for the Gitea API detect if a page is missing apps, and fetch the next page until we have a complete page of apps (this does however not fix the sorting issue)
Move sorting and pagination logic to the client side (we already have a table component for this, but it might be resource intensive for the user's browser when fetching 990 app metadatas in dev)
Add these features ourselves to Gitea's open source repo
Description
Currently, we're using Gitea's API for sorting and pagination handling when fetching apps on the dashboard.
The challenge here is that Gitea's API does not support sorting by
updatedByordescription, and it also cannot use "excluding keywords" like-datamodels. In order to only show the actual apps, not including data models, we have to filter on the client side, after having received all repos.This leads to bugs like the one shown below, where we fetch a page with 5 rows, filter out 1, and the user ends up with 4 rows being displayed, even though the page size is set to 5:
Potential solutions: