-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ktable): store offset of next page in nextOffset #2355
Conversation
✅ Deploy Preview for kongponents-sandbox ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for kongponents ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
dcb06c8
to
69add7e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes here look correct to me; we need to thoroughly test both with offset and cursor pagination to ensure all scenarios are functional
69add7e
to
cc17d53
Compare
cc17d53
to
6e05744
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look good to me. I've pulled these changes into konnect-ui-apps for sanity check: https://github.com/Kong/konnect-ui-apps/pull/4037. I'll tag a few people to check offset and cursor pagination functionality in different apps just to make sure we don't miss anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
## [9.4.1](v9.4.0...v9.4.1) (2024-08-27) ### Bug Fixes * **ktable:** store offset of next page in nextOffset ([#2355](#2355)) ([bf1821e](bf1821e))
🎉 This PR is included in version 9.4.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
This PR includes:
nextOffset
, so that the originaloffset
ref will always equal the offset of the current page.