-
Notifications
You must be signed in to change notification settings - Fork 400
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 #3405. Updated react-data-grid to latest version #3438
Conversation
.scan((acc) => acc + 1, 0) | ||
.map(scrollToTopCounter => ({scrollToTopCounter})) | ||
.startWith({}), | ||
(props, newProps) => ({ |
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.
I only see one Observable, why props and newProps?
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.
They are 2 observable merged into one. Maybe newProps is misleasing. Should i call it forceScrollProps?
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.
Yes, maybe, should make it more clear, thanks
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.
Just a couple of comments / questions, otherwise looks good
use a better name for `scrollToTopCounter` props
Description
The issue for horizontal scrolling has been fixed in the latest version (see issue).
I had also to port some extension to the latest version:
immutable
dependency (it doesn't work without)Grid
object has been changed and the old overrides that implemented this didn't work anymore. Implemented instead aforceScrollTop
enhancer +scrollToTopCounter
property to use to force scroll.RowRenderer
have to userenderBaseRow
to preserveref
function and so support frozen (ex - blocked) columns (tipically selection column and "zoom to feature" button in the feature grid). Otherwise the frozen columns didn't worked anymireIssues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
Grid can not be scrolled horizontally
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
I suggest to re-do all the integration tests on the feature grid.