-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
[discussion] Preparing v6 #30660
Comments
What change does this fall under?
I'm curious for the reason behind removing Edit: It looks like it was added in f98d52b so I believe the reason must be that |
Hi everyone, not sure this is the best place to post my request, but it seems to me that V6 of MUI should also bring some "standardization" in a way to manipulate the styles. Let me give you an example. Do not hesitate to move my comment elsewhere I spent a couple of hours to find how to style the " I came up with this solution for the "MuiLink" component in the createTheme: styleOverrides: {
root: () => {
return {
borderColor: themePalette.SECONDARY_COLOR,
"&:hover": { //<--- :hover is also working. the & is not mandatory
borderColor: themePalette.SECONDARY_COLOR,
color: "white",
},
"&.active": { // <--- .active is not working... Need the &
background: themePalette.THIRD_COLOR,
color: themePalette.SECONDARY_COLOR,
fontWeight: "bold",
},
};
},
}, That might be obvious for you BUT here is the trick: I'm not very familiar with pure CSS, maybe in a CSS file this is also working this way, but for TS or JS, a standardization might be really powerful. Anyway, your library is so great. Thks for your job and happy new year. |
It would be great to know your thoughts and to know whether you consider:
|
This comment was marked as resolved.
This comment was marked as resolved.
@o-alexandrov I have added a new section for big feature ideas for v6.
|
How about simplifying MUI's codebase on how you do animation by adopting framer-motion, Transitions in particular?
|
@o-alexandrov I saw few days ago that the Chakra UI team noted in their 3.0 roadmap that they want to remove the framer motion dependency:
their roadmap post is here: chakra-ui/chakra-ui#7180 so maybe doing that would actually be the best solution, allow framer motion or any other motion library to replace (mui) motion, similar to how it is done for date libraries and probably similar to the idea of removing the dependency on emotion to allow other css-in-js libraries as alternatives (see style engine discussion #34826 that emerged after the nextjs / server components discussion started: #34896) |
With regard to static CSS extraction, would/could this cover use cases where theme configs are loaded dynamically at runtime? For example, I have an app that has a different color scheme based on the customer that it's deployed for and the theme config is fetched on page load and applied to the app. Would it be possible to fetch the theme configs at build time? Or maybe export the theme config variables as global CSS variables that can then be overridden at runtime? |
@nunesunil The recommended way is to wrap your ThemeProvider and make that one Client component, then place it on the RootLayout, which remains as RSC. I have done it for my ThemeProvider and any other providers that I had at the root and it works. |
#31885 How is support for Gap looking? |
Are there plans to support server components (primarily with Next.js) in the initial |
There is this: It is added to the v6 milestone |
Hello everyone, For a much smoother migration experience, we’ve decided to split the next year’s major into two releases. Generally speaking, it’s a new release strategy we’re adopting after hearing feedback from many of you about the v4 → v5 migration—more frequent and less breaking majors seem like the way to go. With that, here’s what you can expect for Material UI v6 and v7:
Check out the public Material UI GitHub project for an overview of this plan and the respective GitHub milestones for a detailed list of what will be included in each release. We also put out this announcement as a blog post! As always, feel free to continue the discussion here or on a specific issue. Let us know if there’s anything else you’d like to see included in each major! |
Can you please consider to drop React 17 support?
React 18 is released in May 2022, so it will be more than two years since the release of the last React's major by the time Material UI v6 is released. |
Can you please consider adding the select options to accept any value To fix the issue we are facing with other libraries like react-hook-form |
@o-alexandrov hi! Could you please open an RFC for that so we can discuss it? Please point out the benefits of removing support. We would also have to analyze the ratio of downloads between both versions. @ahmed-saber hi! Is there a GitHub issue describing the issue you're facing? |
It would be great if mui could implement a component for numbers. I know there is already a github issue for that but this is already open for years: Number input component. I don't know how a web application can be done without entering numbers. Therefore, I find this component to be one of the most important missing things from mui. Besides: Thank you for your work |
As of now, there is no way to globally set a scale factor in MUI. Material-UI supports this from Material-UI 3 (uncertain about versions earlier than 3). I have been searching for a solution in MUI for a while, hoping for at least a one-time set workaround, but have not found anything that would apply the change to the entire theme. I believe this could be a valuable addition that would assist in maintaining consistent website design across various displays. |
Edited by @DiegoAndai: Moved accepted ideas/issues into either the v6 milestone, the v7 milestone, or this list of brainstorm ideas
This is an umbrella issue that centralizes and lists all the potential improvements that we can consider in MUI Core v6. The potential improvements being listed here require breaking changes. We do not intend to ship v6 in 2022. We plan, as much as possible, to release the next major features in minor versions without breaking changes.
Big features
Other changes
For a detailed list of changes, please visit the Material UI: v6 milestone. If you're looking for a particular change, you can also search issues filtering by that milestone.
Promotions
The text was updated successfully, but these errors were encountered: