-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[DataGrid] Improve the handling of events (rm capture, add event, add new props) #1158
Conversation
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 like the idea of using the synthetic event system of React rather than a native event. This should help/solve #891.
Should we bind the events if there is a renderCell? How about with a renderEditCell? |
If we keep renderCell and renderEditCell customizing the children of a cell, not the Cell itself, I think that we should keep the binding of the events in the internal of the data grid. So no. By removing the event capture, we make it possible for developers to hook into event.nativeEvent inside the cells (not the whole Cell but the children). As a side note, it might be interesting to add a test case where we click in a button on a cell, add something in the event, and see this something available in the onRowClick/onCellClick listeners. It gets us one step closer to solving #891 |
Issue with the event serialisation on commodity dataset |
I did some improvements on the storybook. |
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.
You can use the documentation that Sebastian has added to debug the failing visual repression tests: https://github.com/mui-org/material-ui/blob/next/test/README.md#run-the-visual-regression-tests
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.
We need to update the API pages. Hopefully, this pain with incentivize us to work on its automatic generation.
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.
Nice a large refactoring 😁
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Olivier Tassinari <olivier.tassinari@gmail.com>
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.
Great
Just curious when will this be released? |
v4.0.0-alpha-23 should be released already |
Breaking Changes
Fix #1157
Fix #1108
Fix #273
Related to #947
TODO: