-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
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
[material-ui][docs] Add v5 to v6 migration guide #41561
[material-ui][docs] Add v5 to v6 migration guide #41561
Conversation
Netlify deploy previewBundle size report |
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.
👍
Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Signed-off-by: Diego Andai <diego@mui.com>
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.
LGTM cc @siriwatknp we may want to start similar page for the system itself too, or we can consolidate all changes here. Whatever you think will work better.
Add v5 to v6 migration guide. This way, breaking changes can be added as soon as they're introduced.
I followed the existing folder naming convention, which is somewhat confusing as the file names mention the "from" version (
v5
), but the titles mention the "to" branch (v6
). Do you think we should change this? It would be easier if the folder, file names, and content titles matched