-
Notifications
You must be signed in to change notification settings - Fork 27
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
Issue 40 large dataset #1152
Issue 40 large dataset #1152
Conversation
✅ Deploy Preview for papaya-valkyrie-395400 canceled.
|
905bfd0
to
a9bcbe5
Compare
16ee53c
to
5f8eb2c
Compare
keySet.reset({ from: 0, to: 35 }); | ||
console.log(keySet.toDebugString()); | ||
console.log(` nextKeyValue ${keySet["nextKeyValue"]}`); |
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.
Should we remove the logs now that this is resolved?
firstRowRef.current = firstRow; | ||
setRange({ | ||
from: firstRow, | ||
to: firstRow + viewportRowCount + 1, |
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.
In other places, we're not adjusting index by + 1
for to:
when setting range. Is this intentional here?
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.
Good spot, this used to be the norm, but I realised when writing tests that the +1 was not correct. Leaving this one is an oversight. fixed.
5f8eb2c
to
8a130c2
Compare
UI Table support for large datasets (> 1 million rows)
supports scrolling through full dataset with