feat: Add mapResults to PaginationResult#106
Merged
luanpotter merged 1 commit intomainfrom Jan 26, 2026
Merged
Conversation
f07619e to
164b7be
Compare
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 was extracted from the version on backend, keeps both of them in line for ease of replacement.
NOTE: as per our existing impl, this DOES NOT update the page size or any page computations. We mostly use it to batch process the list. To make a simple "couldn't do it with the other one" test, I opted to use a filter. I know that particular usage is potentially problematic depending on intent. Happy to change the test or consider alternatives.