You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should implement pagination for the endpoints that get a list of items from the deployer and gateway. This will be useful for CLI users so they can get only a subset of e.g. projects, rather than all of them. It will also be useful for the console, so we can fetch a subset at a time, rather than fetch them all and then paginate them in the browser.
Implement pagination for project list (”/projects” endpoint on the router in gateway/api/latest)
Implement pagination for deployment list
Consider whether we should follow this up with some filtering, e.g. should we be able to filter project list by project state?
Suggestion or Example of how the feature would be used
Are there more endpoints we should implement this for? Should we consider using cursor pagination for this?
Duplicate declaration
I have searched the issues and this feature has not been requested before.
The text was updated successfully, but these errors were encountered:
Describe the feature
We should implement pagination for the endpoints that get a list of items from the deployer and gateway. This will be useful for CLI users so they can get only a subset of e.g. projects, rather than all of them. It will also be useful for the console, so we can fetch a subset at a time, rather than fetch them all and then paginate them in the browser.
Suggestion or Example of how the feature would be used
Are there more endpoints we should implement this for? Should we consider using cursor pagination for this?
Duplicate declaration
The text was updated successfully, but these errors were encountered: