Skip to content
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

Update dependency @mui/material to v5.12.3 #130

Merged
merged 1 commit into from
May 2, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@mui/material (source) 5.12.2 -> 5.12.3 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Release Notes

mui/material-ui

v5.12.3

Compare Source

May 2, 2023

A big thanks to the 18 contributors who made this release possible. Here are some highlights ✨:

  • all planned breaking changes for Base UI are done. The first beta release should come next week 🎉
  • 🐛 bug fixes and 📚 documentation improvements.
@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
Breaking changes
  • The component prop is no longer supported because it can be replaced with the slots API. This is how the transformation will look like:

     <Button
    -  component="span"
    +  slots={{ root: "span" }}
     />

    If using TypeScript, the custom component type should be added as a generic on the Button component.

    -<Button
    +<Button<typeof CustomComponent>
       slots={{ root: CustomComponent }}
       customProp="foo"
     />

    There is codemod that you can run in your project to do the transformation:

    npx @&#8203;mui/codemod v5.0.0/base-remove-component-prop <path>

    The full documentation about the codemod can be found here.

    This is the list of PR related to this change:

  • ​[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 <slot_name>Ref, which matches the get<slot_name>Props 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<Element>
    4. Naming and typing of the forwarded ref in unstyled components were standardized - it's forwardedRef: React.ForwardedRef (unless a more specific type is needed).
    5. The shape of the definition of unstyled components was standardized - it's React.forwardRef(function Component(props: Props, forwardedRef: React.Ref) { ... });. Specifically, the generic parameters of forwardRef were removed as they are specified in function arguments.
Changes
Docs
Core

All contributors of this release in alphabetical order: @​cherniavskii, @​DavidBoyer11, @​hbjORbj, @​jakub-stastny, @​joserodolfofreitas, @​maxdestors, @​michaldudak, @​mj12albert, @​mnajdova, @​navedqb, @​nicolas-ot, @​oliviertassinari, @​PunitSoniME, @​sai6855, @​samuelsycamore, @​siriwatknp, @​varunmulay22, @​ZeeshanTamboli


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@PacoVK PacoVK merged commit 27ae7ce into main May 2, 2023
@PacoVK PacoVK deleted the renovate/material-ui-monorepo branch May 2, 2023 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant