Pagination components refactoring #1062
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.
Description
This PR is a refactoring aimed at simplifying and homogenizing pagination across the project:
Paginable
interface is introduced; any component that can handle pagination, be it async or sync, should implement this APIui/layout
module, there's 4 of them (prev/next buttons, pagination dots, page numbers from the Editor and page selector from the organizations page in the Datahub)Architectural changes
Moved several components from ui/elements to ui/layout
Quality Assurance Checklist
breaking change
labelbackport <release branch>
label