From 33cd143a96ac780c6682796fcc96f253f3438967 Mon Sep 17 00:00:00 2001 From: Diego Andai Date: Fri, 15 Mar 2024 10:47:24 -0300 Subject: [PATCH] Point to material-ui repo's HEAD on codemods link --- .../bringing-consistency-to-material-ui-customization-apis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/bringing-consistency-to-material-ui-customization-apis.md b/docs/pages/blog/bringing-consistency-to-material-ui-customization-apis.md index 3159fcaff8ea24..74be270a250e02 100644 --- a/docs/pages/blog/bringing-consistency-to-material-ui-customization-apis.md +++ b/docs/pages/blog/bringing-consistency-to-material-ui-customization-apis.md @@ -65,6 +65,6 @@ Because of these issues, composed CSS classes will be deprecated and eventually This initiative aims to improve the developer experience for the Material UI community. To provide the smoothest migration from the inconsistent APIs, they will be deprecated first and removed later, giving you plenty of time to adjust. -With each deprecation, we'll update the [migration guide](https://mui.com/material-ui/migration/migrating-from-deprecated-apis/) and provide [codemods](https://github.com/mui/material-ui/tree/master/packages/mui-codemod#deprecations) to simplify the process. +With each deprecation, we'll update the [migration guide](https://mui.com/material-ui/migration/migrating-from-deprecated-apis/) and provide [codemods](https://github.com/mui/material-ui/tree/HEAD/packages/mui-codemod#deprecations) to simplify the process. As always, we'd love to hear what you think! Please [open a GitHub issue](https://github.com/mui/material-ui/issues/new/choose) if you encounter any unexpected behavior with the standardized APIs or if you have any other suggestions you'd like us to discuss.