hotfix: pagination key ... duplicate, change key#307
Merged
zaidaiman merged 1 commit intoSep 17, 2025
Conversation
🦋 Changeset detectedLatest commit: 2673812 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
Main Description
hotfix : fix pagination key where pages is set to key and some design use initialPage ... middlePage ... endPage
where ... causes react to throw error due to ... duplication.
Type of change
[✅ ] fix feature
Affected endpoints
Backend
Checklist
[] My code follows the style guidelines of this project
[✅] I have performed a self-review of my code
[✅] I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
[✅] My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works