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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Right now, we have all the resources listed on one page for the directory listing. Would be great if we could partition this into pages of some fixed size.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Having page listings on the directory listing so that even if we have our API return all entries (i.e. not doing pagination on the backend side as well), at least we have separation into like 20 resources / page so it doesn't cause lag on the page if there are, say, 500 resources.
Additional context
Add details, any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Right now, we have all the resources listed on one page for the directory listing. Would be great if we could partition this into pages of some fixed size.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Having page listings on the directory listing so that even if we have our API return all entries (i.e. not doing pagination on the backend side as well), at least we have separation into like 20 resources / page so it doesn't cause lag on the page if there are, say, 500 resources.
Additional context
Add details, any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: