-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[pickers] Avoid some nested imports in @mui/utils
#9172
Conversation
Netlify deploy previewNetlify deploy preview: https://deploy-preview-9172--material-ui-x.netlify.app/ Updated pagesNo updates. These are the results for the performance 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.
Are we sure we want to do this?
For me it's going against what we are trying to achieve in mui/material-ui#35840
Not at all, that's why I asked for your review 😉 |
I think the issue is that vs So for me, the clean fix would be to move all the utils (or at least the one used in other packages) into folders with an |
I share @flaviendelangle's concerns about not using nested imports (especially when we try to teach other developers to use them). If introducing directories solves the problem, we can do it. In the future, we can explicitly say it's a private package, then reorganize it a bit more (e.g., place all the prop-types utilities into one directory etc.). |
@michaldudak @alexfauquette @LukasTy If I open a PR tomorrow on the core to create the folders, I think we can fix the problem without having the intermediate step proposed in this PR. |
This PR has already been open for 2 weeks already. 🙈 |
Here is the PR: mui/material-ui#37586 |
Fix #9170