-
Notifications
You must be signed in to change notification settings - Fork 303
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
Release list pagination, frontend part #482
Comments
Hii, |
Which pointers do you need? As for general Open Source, you'll need to create a "pull request" on GitHub, there are plenty of guides on Internet how to do it. |
Hey, I would love to try this out. Can it still be assigned to me? |
@eyalyehia Feel free to bring PR for it, I usually don't assign issues. The fact of draft PR created serves as better proof of you working on it. |
Relates to #372 and 166.
Due to performance issues, we need to employ the pagination approach for the list of releases displayed. Now that we have migrated to ReactJS, it should be easier to implement.
The frontend side of implementation should be classic pagination at the bottom of the list, and using pagination should cause backend API request with corresponding
offset
andlimit
query string parameters added. The place wheretotal
number of items is returned from backend should for now be assumed and marked with "TODO", so when backend implements it, the frontend is modified to utilize it.For now, the backend would just ignore those parameters and will still return full list. The backend part will be done separately.
The text was updated successfully, but these errors were encountered: