diff --git a/CHANGELOG.old.md b/CHANGELOG.old.md index 627da516f56de3..90109a4b3ff19a 100644 --- a/CHANGELOG.old.md +++ b/CHANGELOG.old.md @@ -5668,7 +5668,6 @@ A big thanks to the 18 contributors who made this release possible. Here are som The full documentation about the codemod can be found [here](https://github.com/mui/material-ui/blob/master/packages/mui-codemod/README.md#base-remove-component-prop). This is the list of PR related to this change: - - [Button][base] Drop `component` prop (#36677) @mnajdova - [Badge][base] Drop `component` prop (#37028) @hbjORbj - [FormControl][base] Drop component prop (#37031) @hbjORbj @@ -5692,7 +5691,6 @@ A big thanks to the 18 contributors who made this release possible. Here are som - [base] Improve API consistency (#36970) @michaldudak Brought consistency to Base UI components and hooks' parameters and return values: - 1. Whenever a hook needs a ref, it's now called `Ref`, which matches the `getProps` in the return value. 2. All hooks that accept external refs now return merged refs, making combining multiple hooks on one element easier. This was proven necessary in several compound components (like menuItem being both a button and a list item). The type of this value is `React.RefCallback` as using the more general `React.Ref` caused variance issues. 3. Type of accepted refs is standardized to `React.Ref` @@ -6555,7 +6553,6 @@ A big thanks to the 15 contributors who made this release possible. Here are som #### Breaking changes - [Joy] Replace `Joy[Component]` classname with `Mui[Component]` classname for all slots of components (#35718) @hbjORbj - - Renames the classname prefix of all Joy UI components from `'Joy'` to `'Mui'`. ```diff @@ -6568,7 +6565,6 @@ A big thanks to the 15 contributors who made this release possible. Here are som You can use this [codemod](https://github.com/mui/material-ui/blob/master/packages/mui-codemod/README.md#joy-rename-classname-prefix) to help with the migration. - [Joy] Replace `row` prop with `orientation` prop in all Joy UI components (#35721) @hbjORbj - - Transforms `row` prop to `orientation` prop across `Card`, `List` and `RadioGroup` components in Joy UI. ```diff @@ -6633,7 +6629,6 @@ A big thanks to the 13 contributors who made this release possible. Here are som #### Breaking changes - [SliderUnstyled] Improved logic for displaying the value label (#35805) @ZeeshanTamboli - - The `valueLabelDisplay` prop is removed from `SliderUnstyled`. The prop was not working as intended in `SliderUnstyled` (See #35398). You can instead provide a `valueLabel` slot with the `slots` prop API to show the value label: ```diff @@ -6642,7 +6637,6 @@ A big thanks to the 13 contributors who made this release possible. Here are som ``` The following demo shows how to show a value label when it is hovered over with the thumb: https://v6.mui.com/base-ui/react-slider/#value-label - - The following classes are removed from `sliderUnstyledClasses` since they are not needed for the value label: ```diff @@ -6653,7 +6647,6 @@ A big thanks to the 13 contributors who made this release possible. Here are som ``` In the custom value label component, you can define your own classNames and target them with CSS. - - The `SliderValueLabelUnstyled` component is removed from SliderUnstyled. You should provide your own custom component for the value label. - To avoid using `React.cloneElement` API in value label, the component hierarchy structure of the value label is changed. The value label is now inside the Thumb slot - `Thumb` -> `Input`, `ValueLabel`. @@ -7043,7 +7036,6 @@ A big thanks to the 15 contributors who made this release possible. Here are som #### BREAKING CHANGE - [Joy] Add `slots`/`slotProps` props to the typing of all components and apply `useSlot` to all components (#34997) @hbjORbj - - Change all occurrences of `components` and `componentsProps` props in Joy UI components to `slots` and `slotProps`, respectively. ```diff @@ -7396,7 +7388,6 @@ A big thanks to the 10 contributors who made this release possible. Here are som #### BREAKING CHANGE - [base] `components` -> `slots` API rename (#34693) @michaldudak - - Change all occurrences of components and componentsProps props in Base components to slots and slotProps, respectively. - Change casing of slots' fields to camelCase @@ -7547,7 +7538,6 @@ A big thanks to the 7 contributors who made this release possible. Here are some The `enableColorScheme` prop has been removed from `CssVarsProvider` and `getInitColorScheme` (both Material UI and Joy UI). Migration: - - **Material UI**: you can enable the CSS color scheme via ``. - **Joy UI**: it is enabled automatically if you use ``, [see the docs](https://mui.com/joy-ui/react-css-baseline/). @@ -9800,7 +9790,6 @@ A big thanks to the 22 contributors who made this release possible. Here are som Note: the utility components, such as ClickAwayListener, NoSsr, Portal, and TextareaAutosize continue to be exported from both `@mui/material` and `@mui/base`. If you're encountering build errors after upgrading @mui/material, do the following: - 1. Install @mui/base: npm install @mui/base or yarn add @mui/base 2. Make sure the version of @mui/base match the version of @mui/material 3. Change the import paths of unstyled components from @mui/material to @mui/base, e.g.: @@ -11279,7 +11268,6 @@ A big thanks to the 26 contributors who made this release possible. Here are som - [core] Update `.browserslistrc` file (#27788) @DanailH The targets of the default bundle have changed: - - Chrome 90 (up from 84) - Edge 91 (up from 85) - Safari 14 (macOS) (up from 13.1) and 12.4 (iOS) (up from 12.2) @@ -11906,7 +11894,6 @@ A big thanks to the 18 contributors who made this release possible. Here are som #### Breaking changes - [Menu] Use ButtonBase in MenuItem (#26591) @siriwatknp - - Change the default value of `anchorOrigin.vertical` to follow the Material Design guidelines. The menu now displays below the anchor instead of on top of it. You can restore the previous behavior with: ```diff @@ -12000,7 +11987,6 @@ A big thanks to the 18 contributors who made this release possible. Here are som - [core] Remove `unstable_` prefix on the `useThemeProps` hook (#26777) @mnajdova The following utilities were renamed to not contain the `unstable_` prefix: - - `@material-ui/sytstem` ```diff @@ -12385,7 +12371,6 @@ A big thanks to the 14 contributors who made this release possible. Here are som - [Tabs] Update `min` & `max` width and remove `minWidth` media query (#26458) @siriwatknp Update the implementation to better match Material Design: - - Tab `minWidth` changed from `72px` => `90px` (without media-query) according to [material-design spec](https://m2.material.io/components/tabs#specs) - Tab `maxWidth` changed from `264px` => `360px` according to [material-design spec](https://m2.material.io/components/tabs#specs) @@ -12816,7 +12801,6 @@ A big thanks to the 17 contributors who made this release possible. Here are som - [Autocomplete] Rename values of the reason argument (#26172) @m4theushw Rename the values of the reason argument in `onChange` and `onClose` for consistency: - 1. `create-option` to `createOption` 2. `select-option` to `selectOption` 3. `remove-option` to `removeOption` @@ -12841,7 +12825,6 @@ A big thanks to the 17 contributors who made this release possible. Here are som ``` - [core] Remove `createStyles` from `@material-ui/core` (#26018) @mnajdova - - The `createGenerateClassName` module is no longer exported from `@material-ui/core/styles`. You should import it directly from `@material-ui/styles`. ```diff @@ -13835,7 +13818,6 @@ A big thanks to the 30 contributors who made this release possible. Here are som - 👩‍🎤 Convert 32 components to emotion. Around 64% of the components have been migrated so far, thanks to the help of the community. We aim to migrate them all before the end of Q1 2021. The podium of the most active community members in the migration 🏆: - 1. @natac13 x17 2. @vicasas x5 3. @kodai3 x4 @@ -15049,14 +15031,12 @@ Here are some highlights ✨: You can read the [introduction blog post](https://medium.com/material-ui/introducing-material-ui-design-system-93e921beb8df) that we did for MUI System two years ago. The system is meant to solve the following problems: - 1. Naming things is hard. How should a class name, JSS style rule, or styled component be named? 2. Jumping between JS and CSS in the editor wastes time. This is particularly true as the complexity (LOCs/# of elements) of a component increases. It's still true when using the `styled()` API. 3. Introducing a `makeStyles` for the first time in a component is daunting. For example, it's why https://github.com/vscodeshift/material-ui-codemorphs#add-usestyles-hook exists. What if we had less code to type, gaining velocity when writing styles? 4. Pulling values out from the theme can be cumbersome. How can we make it less painful to increase the usage of design tokens? This new iteration of MUI System brings two major improvements: - - It moves from the support of a subset of CSS to the support of a superset of CSS. Learning the shorthand is optional. It's no longer necessary to moving back to styled() when MUI System doesn't support a specific CSS property. - It moves from support on Box only to any core component (starting with the slider). @@ -15088,7 +15068,6 @@ Here are some highlights ✨: - [Popper] Upgrade to popper.js to v2 (#21761) @joshwooding This third-party library has introduced a lot of changes.
You can read [their migration guide](https://popper.js.org/docs/v2/migration-guide/) or the following summary: - - The CSS prefixes have changed: ```diff @@ -15220,7 +15199,6 @@ Here are some highlights ✨: - 📦 Ship modern bundle (#22814) @eps1lon. This is a significant update to the [browsers supported](https://mui.com/material-ui/getting-started/supported-platforms/) by Material UI. The previous policy was defined 2 years ago, and the landscape has evolved since then. The package now includes 4 bundles: - 1. `stable` (default, formerly `esm`) which targets a snapshot (on release) of `> 0.5%, last 2 versions, Firefox ESR, not dead, not IE 11"` 2. `node` (formerly default) which targets a snapshot (on release) of `maintained node versions` 3. `legacy` (new) which is `stable` + IE 11 @@ -15613,7 +15591,6 @@ Here are some highlights ✨: - [Tabs] Add allowScrollButtonsMobile prop for mobile view (#22700) @GauravKesarwani The API that controls the scroll buttons has been split it into two props: - - The `scrollButtons` prop controls when the scroll buttons are displayed depending on the space available. - The `allowScrollButtonsMobile` prop removes the CSS media query that systematically hides the scroll buttons on mobile. @@ -16023,7 +16000,6 @@ const theme = createMuiTheme({ - [theme] Rename theme keys to defaultProps and styleOverrides (#22347) @mnajdova - [theme] Restructure component definitions (#22293) @mnajdova The components' definition inside the theme were restructure under the `components` key, to allow people easier discoverability about the definitions regarding one component. - 1. `props` ```diff @@ -19892,7 +19868,6 @@ Here are some highlights ✨: If you are not familiar with codemods, [check the library out](https://github.com/facebook/codemod). This is a tool tool to assist you with large-scale codebase refactors. We introduce two new codemods in this release: - - `optimal-imports`: Material UI supports tree shaking for modules at 1 level depth maximum. You shouldn't import any module at a higher level depth. @@ -20998,13 +20973,11 @@ We hope 2-3 weeks of beta will be enough. We plan on releasing v4 stable in May. - [List] Update to match the specification (#15339) @oliviertassinari Rework the list components to match the specification: - - The usage of the `ListItemAvatar` component is required when using an avatar - The usage of the `ListItemIcon` component is required when using a left checkbox - The `edge` property should be set on the icon buttons. - [actions] Rename disableActionSpacing to disableSpacing (#15355) @oliviertassinari - - [CardActions] Rename the `disableActionSpacing` prop `disableSpacing`. - [CardActions] Remove the `disableActionSpacing` CSS class. - [CardActions] Rename the `action` CSS class `spacing`. @@ -21152,7 +21125,6 @@ Here are some highlights ✨: ``` - [Snackbar] Match the new specification (#15122) @oliviertassinari - - Change the dimensions - Change the default transition to from `Slide` to `Grow`. @@ -21244,7 +21216,6 @@ Here are some highlights ✨: #### Breaking Changes - [Typography] Better defaults (#15100) @oliviertassinari - - Change the default variant from `body2` to `body1`. A font size of 16px is a better default than 14px. Bootstrap, material.io or even our documentation use 16px as a default font size. @@ -21568,7 +21539,6 @@ Here are some highlights ✨: - [styles] Remove the old styles modules (#14767) @oliviertassinari Isolation of the styling solution of the core components in a dedicated package. - - Remove the `MuiThemeProvider` component: ```diff @@ -21642,7 +21612,6 @@ Here are some highlights ✨: ![wrapper](https://user-images.githubusercontent.com/3165635/53287870-53a35500-3782-11e9-9431-2d1a14a41be0.png) - [Table] Add dense support (#14561) @leMaik - - We have removed the deprecated numeric property. ```diff @@ -21754,7 +21723,6 @@ Here are some highlights ✨: #### Breaking Changes - [Typography] Remove deprecated Typography variants (#14562) @joshwooding - - Remove the deprecated typography variants. You can upgrade by performing the following replacements: - display4 => h1 - display3 => h2 @@ -21876,7 +21844,6 @@ Here are some highlights ✨: The upgrade path to React 16.8.0 should be pretty easy for our users. Introducing this breaking change in v4 enables the following: - - We can remove the recompose dependency and use the new `React.memo()` API. - Before or after v4 is out, we can gradually migrate the core components to use the Hook API. @@ -21921,7 +21888,6 @@ console.log({ background }); ``` It's consistent with the other projects: - - material-ui => MaterialUI - react-dom => ReactDOM - prop-types => PropTypes @@ -24831,7 +24797,6 @@ Here are some highlights ✨: ### Breaking change - [ButtonBase] Better keyboard focused story (#11090) @oliviertassinari - - Rename the `keyboardFocused` feature `focusVisible` in order to follow the CSS specification wording: https://drafts.csswg.org/selectors-4/#the-focus-visible-pseudo - Give up on the `classes` property to host the focus visible feature. The fact that the classes don't cascade was making it hard to use. Instead, we rely on a `focusVisibleClassName` property. This is allowing any component along the rendering chain to use the feature. For instance, a Switch component: Switch > SwitchBase > IconButton > ButtonBase. @@ -25715,7 +25680,6 @@ It's making our components less biased around the svg icon vs font icon choice. ``` - [theme] Further simplification & standardization (#10015) @mbrookes - - Most component specific `theme.palette.background` colors have been removed. The affected components use `theme.palette.grey` instead. Shift the values of `theme.palette.grey` if you wish to lighten or darken these as a whole; this will maintain the contrast relationship between them. (Paper remains in the theme, as it is used across multiple components.) - `theme.palette.common.fullBlack` and `fullWhite` have been removed. Components that used these values now use `theme.palette.common.black` and `white` instead. - `theme.palette.common.transparent` has been removed. Components that used this value now use `'transparent'` directly. @@ -25857,7 +25821,6 @@ Here are some highlights ✨: ### Breaking change - [palette] Keep simplifying the solution (#9876) @oliviertassinari - - Remove the contrast color from our API. This color variation hasn't proven itseft to be useful enough. ```diff @@ -25866,7 +25829,6 @@ Here are some highlights ✨: ``` Instead, you can use the `color="inherit"` property or use the `theme.palette.XXX.contrastText` value. - - Rename `accent` to `secondary`. We have removed the accent indirection to be closer to the object people are providing to customize the palette. ```diff @@ -27593,7 +27555,6 @@ A big thanks to the 12 contributors who made this release possible. ``` - [theme] Simplification of the API (#7934) @oliviertassinari - - If you are using a direct import of `material-ui/styles/theme`, the path changed: ```diff diff --git a/docs/data/material/components/app-bar/app-bar.md b/docs/data/material/components/app-bar/app-bar.md index 2fdafabb2cfab4..34cc4a1a566e79 100644 --- a/docs/data/material/components/app-bar/app-bar.md +++ b/docs/data/material/components/app-bar/app-bar.md @@ -123,7 +123,6 @@ A floating action button appears on scroll to make it easy to get back to the to #### Arguments 1. `options` (_object_ [optional]): - - `options.disableHysteresis` (_bool_ [optional]): Defaults to `false`. Disable the hysteresis. Ignore the scroll direction when determining the `trigger` value. - `options.target` (_Node_ [optional]): Defaults to `window`. - `options.threshold` (_number_ [optional]): Defaults to `100`. Change the `trigger` value when the vertical scroll strictly crosses this threshold (exclusive). diff --git a/docs/data/material/guides/api/api.md b/docs/data/material/guides/api/api.md index 70712f8bcea00e..ab8aa841ab3b1a 100644 --- a/docs/data/material/guides/api/api.md +++ b/docs/data/material/guides/api/api.md @@ -89,7 +89,6 @@ Nested components inside a component have: ### Prop naming - **Boolean** - - The default value of a boolean prop should be `false`. This allows for better shorthand notation. Consider an example of an input that is enabled by default. How should you name the prop that controls this state? It should be called `disabled`: ```jsx diff --git a/docs/data/material/integrations/interoperability/interoperability.md b/docs/data/material/integrations/interoperability/interoperability.md index 2e01ecfc5cbfab..388ecd1a5bf3d1 100644 --- a/docs/data/material/integrations/interoperability/interoperability.md +++ b/docs/data/material/integrations/interoperability/interoperability.md @@ -634,7 +634,6 @@ If you use a different framework, or already have set up your project, follow th ``` 3. Add the `important` option, using the id of your app wrapper. - - For Next.js projects, use `#__next`. **Note for Next.js 13+ Users (App Router)**: You must now manually add `id="__next"` to your root element (typically ``), as Next.js no longer adds it automatically: ```tsx diff --git a/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md b/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md index 456eb1cdc0933f..4a236b308b7fed 100644 --- a/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md +++ b/docs/data/material/integrations/tailwindcss/tailwindcss-v4.md @@ -417,18 +417,18 @@ If you want to use Material UI theme tokens in your Tailwind CSS classes, copy /* Material UI typography utilities */ @utility typography-* { - font: --value(--font- *); + font: --value(--font-*); } /* Material UI overlay utilities */ @utility overlay-* { - background-image: --value(--overlay- *); + background-image: --value(--overlay-*); } /* Material UI elevation utilities */ @utility elevation-* { - background-image: --value(--overlay- *); - box-shadow: --value(--shadow- *); + background-image: --value(--overlay-*); + box-shadow: --value(--shadow-*); } ``` diff --git a/docs/data/material/migration/migration-v3/migration-v3.md b/docs/data/material/migration/migration-v3/migration-v3.md index b42cd2466f2969..b7014bcefd9bfd 100644 --- a/docs/data/material/migration/migration-v3/migration-v3.md +++ b/docs/data/material/migration/migration-v3/migration-v3.md @@ -269,7 +269,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g ### List - [List] Rework the list components to match the specification: - - The `ListItemAvatar` component is required when using an avatar. - The `ListItemIcon` component is required when using a left checkbox. - The `edge` property should be set on the icon buttons. @@ -342,7 +341,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g ### Snackbar - [Snackbar] Match the new specification. - - Change the dimensions - Change the default transition from `Slide` to `Grow`. @@ -470,7 +468,6 @@ This change is explained in more detail in the [TypeScript guide](/material-ui/g ``` It's consistent with other React projects: - - material-ui => MaterialUI - react-dom => ReactDOM - prop-types => PropTypes diff --git a/docs/data/system/styled/styled.md b/docs/data/system/styled/styled.md index 87520005039660..eeff9422c74ca1 100644 --- a/docs/data/system/styled/styled.md +++ b/docs/data/system/styled/styled.md @@ -36,7 +36,6 @@ It aims to solve the same problem, but also provides the following benefits: 1. `Component`: The component that will be wrapped. 2. `options` (_object_ [optional]): - - `options.shouldForwardProp` (_`(prop: string) => bool`_ [optional]): Indicates whether the `prop` should be forwarded to the `Component`. - `options.label` (_string_ [optional]): The suffix of the style sheet. Useful for debugging. - `options.name` (_string_ [optional]): The key used under `theme.components` for specifying `styleOverrides` and `variants`. Also used for generating the `label`. diff --git a/docs/pages/blog/2019-developer-survey-results.md b/docs/pages/blog/2019-developer-survey-results.md index 5fe727abbc6bfa..f91019fbc00b54 100644 --- a/docs/pages/blog/2019-developer-survey-results.md +++ b/docs/pages/blog/2019-developer-survey-results.md @@ -59,7 +59,6 @@ The prefix corresponds to the number of times the concern was mentioned. It's sorted descending, with the most important concerns first: - 135 **More components:** - - 56 Non-specific - 21 Date picker - 10 Autocomplete @@ -85,7 +84,6 @@ It's sorted descending, with the most important concerns first: - 1 Transfer - 50 **Better customization:** - - 23 Non-specific - 15 Docs - 8 Easier @@ -93,7 +91,6 @@ It's sorted descending, with the most important concerns first: - 1 Colors - 36 **Better documentation:** - - 11 Non-specific - 7 More examples - 5 Beginner tutorials @@ -107,28 +104,24 @@ It's sorted descending, with the most important concerns first: - 1 Server-side rendering - 31 **TypeScript:** - - 14 Non-specific - 13 Migrate more demos - 3 withStyles -> makeStyles - 1 Rewrite - 24 **Performance:** - - 23 Non-specific - 1 Table - 19 **Bundle size** - 17 **Material Design Update** - 16 **styled-components:** - - 10 Support - 6 Migration - 14 **Fewer breaking changes** - 10 **More page layout examples** - 9 **Theme:** - - 3 More colors - 3 Live editor - 1 Non-material font example @@ -137,7 +130,6 @@ It's sorted descending, with the most important concerns first: - 8 **React.StrictMode support** - 8 **React Native support** - 6 **Accessibility:** - - 4 Non specific - 1 Docs - 1 SkipNav diff --git a/docs/pages/blog/2020-q1-update.md b/docs/pages/blog/2020-q1-update.md index c658921501f39c..db88ba3111f4ef 100644 --- a/docs/pages/blog/2020-q1-update.md +++ b/docs/pages/blog/2020-q1-update.md @@ -46,15 +46,12 @@ Here are the most significant improvements since the beginning of the year: - ⚛️ We have worked on improving developer experience inside text editors. - - We have migrated prop descriptions from JSDoc to TypeScript for 60% of the components. Back-and-forths with the documentation API will be less frequent: ![props](/static/blog/2020-q1-update/props.png) - - The color modules come with new previews: ![colors](/static/blog/2020-q1-update/colors.png) - - We have collaborated with [Andy Edwards](https://github.com/jedwards1211) to provide [snippets](https://marketplace.visualstudio.com/items?itemName=vscodeshift.material-ui-snippets) with Visual Studio Code: ![snippets](/static/blog/2020-q1-update/snippets.gif) @@ -98,7 +95,6 @@ We'll do our best, no guarantee! - 🔥 We will start to work on the [next major: v5](https://github.com/mui/material-ui/issues/20012). You can expect the following: - - A feature freeze on v4. - The introduction of deprecation messages in the next v4 minors. These messages will help developers upgrade to v5. - A progressive bug fixes freeze on v4, with the exception of security issues and important bugs. diff --git a/docs/pages/blog/2020-q2-update.md b/docs/pages/blog/2020-q2-update.md index 29f38b8eee2ea2..afbc7bdc00c9fd 100644 --- a/docs/pages/blog/2020-q2-update.md +++ b/docs/pages/blog/2020-q2-update.md @@ -65,7 +65,6 @@ Here are the most significant improvements since March 2020: ``` - 📆 On the [date picker](https://mui.com/x/react-date-pickers/): - - A new `renderInput` API which matches that of the autocomplete component has been added. - The input mask UX has been improved. - Support for `value={null}` has been added. @@ -102,7 +101,6 @@ We'll do our best, no guarantee! These are objectives, no guarantees: - 🏢 We will [hire](/careers/) 3 full-time roles in the team. - - One person on the open-source side to focus on the design system problem (unstyled, theming, styling, etc.): ✅ starting in two months. - One person on the enterprise side to consolidate the development of the advanced components: 🚧 Work in progress. - One person on a role yet to defined: 🚧 Work in progress. diff --git a/docs/pages/blog/2021-q1-update.md b/docs/pages/blog/2021-q1-update.md index 2f1c944ff24859..11b30d3867d409 100644 --- a/docs/pages/blog/2021-q1-update.md +++ b/docs/pages/blog/2021-q1-update.md @@ -87,7 +87,6 @@ This new feature removes the need to create a wrapper component. - 🦴 We have migrated a couple of components to the `@mui/base` package. The aim of the package is to host the unstyled and headless (hooks) components. So far, you can only find: - - Backdrop - Badge - Focus trap diff --git a/docs/pages/blog/2021-q2-update.md b/docs/pages/blog/2021-q2-update.md index 0a48c03f56877e..c3986db2589e2e 100644 --- a/docs/pages/blog/2021-q2-update.md +++ b/docs/pages/blog/2021-q2-update.md @@ -26,7 +26,6 @@ Here are the most significant improvements since March 2021. ### Core components - 🔥 We've made enough progress to ship [v5.0.0-beta.0](https://github.com/mui/material-ui/releases/tag/v5.0.0-beta.0). Here are a few statistics to give an idea of the effort that went into it: - - [12 months](/blog/2020-q2-update/#product) of dedicated focus. We stopped work on v4 early on to fully dedicate to v5. - 3,475 pull requests. diff --git a/docs/pages/blog/2021-q3-update.md b/docs/pages/blog/2021-q3-update.md index dfa6311a89d71d..9cc5e786ba25b3 100644 --- a/docs/pages/blog/2021-q3-update.md +++ b/docs/pages/blog/2021-q3-update.md @@ -31,7 +31,6 @@ Here are the most significant improvements since early July 2021. You can read more about it in the [release blog post](/blog/mui-core-v5/). - ✨ We also introduced a brand new [product page](/core/) this quarter to better present what the Core is about. - 🔎 We've reworked the search experience in the docs: - - The component pages now rank before the API pages. - Instead of only displaying up to 5 results, you can scroll for more results. - An icon illustrates the nature of the match; either a page, a header, or a paragraph. @@ -51,7 +50,6 @@ Here are the most significant improvements since early July 2021. - We introduced a new [package of components without styles](https://www.npmjs.com/package/@mui/base), laying the foundations for supporting multiple design systems with headless components. While it was tough to balance the time between working on v5 stable and developing the unstyled components, we still managed to introduce the first few: - - [Autocomplete](/material-ui/react-autocomplete/#useautocomplete) ```jsx diff --git a/docs/pages/blog/2021.md b/docs/pages/blog/2021.md index 58c300cc8d4476..7df447e161d459 100644 --- a/docs/pages/blog/2021.md +++ b/docs/pages/blog/2021.md @@ -74,7 +74,6 @@ We have achieved most of what we could have hoped for. - We have broken down the demos into smaller and focus on one aspect at a time. - We have polished and promoted most of the components that were in the lab to `@mui/material`. - We have introduced many new components: - - [Masonry](/material-ui/react-masonry/) - [Stack](/material-ui/react-stack/) - [Trap Focus](https://v6.mui.com/base-ui/react-focus-trap/) diff --git a/docs/pages/blog/mui-core-v5.md b/docs/pages/blog/mui-core-v5.md index 202cfbda53173d..a6d6dd4ff3a5e0 100644 --- a/docs/pages/blog/mui-core-v5.md +++ b/docs/pages/blog/mui-core-v5.md @@ -120,7 +120,6 @@ After [exploring](https://github.com/mui/material-ui/issues/22342) many differen 1. We have made `styled()` the lowest level primitive to add styles. This API is already known by many. 2. We have defined a common interface with concrete implementations: - - `@mui/styled-engine`: implemented with Emotion (default). - `@mui/styled-engine-sc`: implemented with styled-components - If you are using a different styling library, feel free to contribute a wrapper. For instance, there is [one attempt with goober](https://github.com/mui/material-ui/pull/27776), a library obsessing on bundle size (3kB gzipped). diff --git a/docs/pages/blog/mui-x-v6-alpha-zero.md b/docs/pages/blog/mui-x-v6-alpha-zero.md index 0b7fe97b281eb4..fbee85cca3a1c9 100644 --- a/docs/pages/blog/mui-x-v6-alpha-zero.md +++ b/docs/pages/blog/mui-x-v6-alpha-zero.md @@ -63,14 +63,12 @@ It contains the highlights that will be included in the first versions. - **Extended customization abilities**.\ We want to empower more users to employ the Data Grid for complex use cases. - - [ApiRef in the community package](https://github.com/mui/mui-x/issues/6147). - [Filtering on header](https://github.com/mui/mui-x/issues/6247). - [Use the Data Grid internal components outside the grid](https://github.com/mui/mui-x/issues/2522). - **Improved look & feel**\ We're polishing edges in terms of design and usability. - - [New column menu](https://github.com/mui/mui-x/issues/4929). - [New column visibility panel](https://github.com/mui/mui-x/issues/5700). - [Column resize bar only on hover](https://github.com/mui/mui-x/issues/1623). @@ -83,7 +81,6 @@ It contains the highlights that will be included in the first versions. - **Improved UX**\ In the previous version we focused on developer experience and overall stability of the components. Now we're tackling ways to improve usability. - - [Remove the clock view on time pickers (for desktop)](https://github.com/mui/mui-x/issues/4483). - [Visually edit a range by dragging date markers](https://github.com/mui/mui-x/issues/5311). - [Range shortcuts](https://github.com/mui/mui-x/issues/4563). diff --git a/docs/pages/blog/premium-plan-release.md b/docs/pages/blog/premium-plan-release.md index 80daed392e9ae9..22ea26ad96fafb 100644 --- a/docs/pages/blog/premium-plan-release.md +++ b/docs/pages/blog/premium-plan-release.md @@ -87,7 +87,6 @@ Their last renewal can have a support duration of up to 5 years. - **Cost per developer seat** We're lowering our base price points, particularly for Pro users. Fees are billed annually. - - Pro: $249 → $180/year or $15/month - Premium: $599 → $588/year or $49/month **($444/year - early bird)** diff --git a/docs/pages/blog/v6-beta-pickers.md b/docs/pages/blog/v6-beta-pickers.md index fc2e6b5ea63d49..d67800375f0603 100644 --- a/docs/pages/blog/v6-beta-pickers.md +++ b/docs/pages/blog/v6-beta-pickers.md @@ -111,7 +111,6 @@ Now that you've seen what's fundamentally changed with the Pickers, let's briefl - **Default render input**\ You don't need to provide the usual `TextField` on `renderInput` anymore unless you need it customized. In which case you can do it by: - 1. Customizing through props via `field` and `input` slots ([codebox example](https://codesandbox.io/p/sandbox/customizing-fields-with-props-o66r1c?file=/demo.tsx)). 2. Build a new field component using the Field's headless API (documentation coming soon). 3. Use an entirely [custom text field](https://next.mui.com/x/react-date-pickers/date-picker/#custom-input-component) to suit your use case.