spike: Add pagination to useCollections #31
Draft
Conversation
This file contains hidden or 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
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 is discovery work that was done in conjunction with .... to roughly see what would needed to be added on the stac-react side to integrate into
stac-mapto match prod behavior.This adds pagination logic to the
useCollectionshook so results could be paginated through like current prod behavior if stac-react were to be added as it currently is... this would likely change a bit though with the Tanstack query PR https://github.com/developmentseed/stac-react/pull/27/files# underway.A new version of
stac-reactwas not published,yarn linkwas used for development between thisstac-reactbranch and thestac-mapbranch in developmentseed/stac-map#209.