[Feature] Build Pagination component #33
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notion ticket link
Ticket
Implementation description
Pagination
component for handling pagination ofTable
components. Pagination is handled server-side, so GQL data refetching should be done in theonPageChange
callback parameterPagination
component to Requests table pageNotes
Pagination
componentusePagination
hook is not necessary - again, all of the functionality could be abstracted inside thePagination
componentChecklist
[Feature]
,[Improvement]
or[Fix]
,