feat: pagination data utils #9452
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
runspired
added
🎯 canary
runspired
force-pushed
the
pagination-utils
branch
from
8fc136c
to
c9bdc95
Compare
runspired
force-pushed
the
pagination-utils
branch
from
7bc500e
to
eb39218
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a suite of data-utilities for pagination to go along with
PromiseState / <Await />andRequestState / <Request />Docs (in PR)
Implementation Tracking
Below the Line Features
(features we intend to bake into these primitives but may not be added in this PR)
Note
We do not intend for
<Paginate />to be used to manage Tree and LinkedListstructures, which inherently have different requirements around async loading
and pagination. We are planning a separate suite of data-utils for these structures
in the near future.