fix: resolve duplicate pools in Explore page Pools list#8014
Open
leno23 wants to merge 1 commit intoUniswap:mainfrom
Open
fix: resolve duplicate pools in Explore page Pools list#8014leno23 wants to merge 1 commit intoUniswap:mainfrom
leno23 wants to merge 1 commit intoUniswap:mainfrom
Conversation
Fixes issue Uniswap#7984 where pools were displayed twice in the Pools list. The issue was caused by incorrect client-side pagination logic. The page variable is 0-indexed, but the slice calculation was using 'page * pageSize' which resulted in displaying accumulated pools from previous pages. Changed slice calculation from 'page * pageSize' to '(page + 1) * pageSize' to correctly display only the pools for the current page.
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
1 participant
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.
Fixes issue #7984 where pools were displayed twice in the Pools list.
The issue was caused by incorrect client-side pagination logic. The page variable is 0-indexed, but the slice calculation was using 'page * pageSize' which resulted in displaying accumulated pools from previous pages.
Changed slice calculation from 'page * pageSize' to '(page + 1) * pageSize' to correctly display only the pools for the current page.