Skip to content

[Switch] Make color primary default#26182

Merged
mnajdova merged 6 commits into
mui:nextfrom
vicasas:feature/change-color-switch
May 10, 2021
Merged

[Switch] Make color primary default#26182
mnajdova merged 6 commits into
mui:nextfrom
vicasas:feature/change-color-switch

Conversation

@vicasas

@vicasas vicasas commented May 7, 2021

Copy link
Copy Markdown
Member

Breaking changes

  • [Switch] Make color="primary" the default over secondary. This better matches the material design guidelines.

    -<Switch />
    +<Switch color="secondary" />

One of the material design section #20012

Preview: https://deploy-preview-26182--material-ui.netlify.app/components/switches/

@mui-pr-bot

mui-pr-bot commented May 7, 2021

Copy link
Copy Markdown

Details of bundle changes (experimental)

Generated by 🚫 dangerJS against 70e1166

@mnajdova

mnajdova commented May 7, 2021

Copy link
Copy Markdown
Member

Let’s update the examples so that we can fix the argos differences.

@vicasas

vicasas commented May 7, 2021

Copy link
Copy Markdown
Member Author

@mnajdova The changes of argos I think are expected. Should the demonstrations in the examples show the primary color or secondary?

For the ColorSwitches demo, green was corrected.

@vicasas vicasas added breaking change Introduces changes that are not backward compatible. scope: switch Changes related to the switch. design: material This is about Material Design, please involve a visual or UX designer in the process labels May 7, 2021
@mnajdova

mnajdova commented May 7, 2021

Copy link
Copy Markdown
Member

Ideally, we shouldn't have changes in argos. We should just do:

-<Switch />
+<Switch color="secondary" />

and

-<Switch color="primary"/>
+<Switch  />

Comment thread docs/src/pages/guides/migration-v4/migration-v4.md Outdated
Comment thread docs/src/pages/guides/migration-v4/migration-v4.md Outdated
@oliviertassinari

oliviertassinari commented May 7, 2021

Copy link
Copy Markdown
Member

Ideally, we shouldn't have changes in argos. We should just do:

I'm not so sure, the idea was that "primary" makes more sense. Would we send a contradicting message if the docs don't use it?

Comment thread docs/src/pages/components/switches/ColorSwitches.tsx

@mnajdova mnajdova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mnajdova
mnajdova merged commit c829338 into mui:next May 10, 2021
@vicasas
vicasas deleted the feature/change-color-switch branch May 10, 2021 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change Introduces changes that are not backward compatible. design: material This is about Material Design, please involve a visual or UX designer in the process scope: switch Changes related to the switch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants