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 button migration examples #10903

Merged
merged 1 commit into from
Oct 5, 2023
Merged

Conversation

kyledurand
Copy link
Contributor

WHY are these changes introduced?

Adds an example of what's to be expected when migrating a <Button primary plain monochrome /> element. I don't think we don't want to default to a new style, like plain monochrome which might be the safest, because consumers may want to opt for the plain variant.

So we just insert a comment and defer to the team / section responsible

Copy link
Contributor

@laurkim laurkim left a comment

Choose a reason for hiding this comment

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

💯 🌟

@kyledurand kyledurand merged commit 410b538 into next Oct 5, 2023
7 checks passed
@kyledurand kyledurand deleted the update-button-migration-examples branch October 5, 2023 22:05
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
### WHY are these changes introduced?

Adds an example of what's to be expected when migrating a `<Button
primary plain monochrome />` element. I don't think we don't want to
default to a new style, like `plain monochrome` which might be the
safest, because consumers may want to opt for the `plain` variant.

So we just insert a comment and defer to the team / section responsible
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
### WHY are these changes introduced?

Adds an example of what's to be expected when migrating a `<Button
primary plain monochrome />` element. I don't think we don't want to
default to a new style, like `plain monochrome` which might be the
safest, because consumers may want to opt for the `plain` variant.

So we just insert a comment and defer to the team / section responsible
AnnaCheba pushed a commit to AnnaCheba/polaris that referenced this pull request Apr 22, 2024
### WHY are these changes introduced?

Adds an example of what's to be expected when migrating a `<Button
primary plain monochrome />` element. I don't think we don't want to
default to a new style, like `plain monochrome` which might be the
safest, because consumers may want to opt for the `plain` variant.

So we just insert a comment and defer to the team / section responsible
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.

2 participants