-
-
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] Refactor: create base MenuList props #16481
Conversation
Deploy preview: https://deploy-preview-16481--material-ui-x.netlify.app/ |
autoFocus?: boolean; | ||
autoFocusItem?: boolean; |
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 instead of these have enum for autoFocus
to cover both cases?
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 thought about it but I chose to keep the API material compatible instead. I could be convinced to switch it though.
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.
If that was the general approach so far (to be close to material) then let's leave it. Otherwise, I think that enum is more generic and neutral and more flexible for potential updates
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 approach is mixed, some components are directly compatibles, others are reworked when the material API is too hard to adapt for other design-systems. I'll leave it as it is for now, I might change it once I start implementing bindings for other design-systems.
Part of the design-system agnostic work.
Create base MenuList props. These are directly compatible with material props.