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

Add default parameters to each border radius mixin #31571

Merged
merged 3 commits into from
Sep 1, 2020

Conversation

jeremyvii
Copy link
Contributor

This addresses my feature request (#31515) by adding a default parameter to each border radius mixin. The default value used is the $border-radius SCSS variable.

@jeremyvii jeremyvii requested a review from a team as a code owner September 1, 2020 17:10
Copy link
Member

@ffoodd ffoodd left a comment

Choose a reason for hiding this comment

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

LGTM, very handy indeed.

@mdo mdo added this to Inbox in v5.0.0-alpha2 via automation Sep 1, 2020
@mdo
Copy link
Member

mdo commented Sep 1, 2020

Can you add a note to the Migration guide about the mixin now having a default value?

Copy link
Member

@mdo mdo left a comment

Choose a reason for hiding this comment

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

Thanks!

v5.0.0-alpha2 automation moved this from Inbox to Approved Sep 1, 2020
@mdo mdo merged commit 1503aa1 into twbs:main Sep 1, 2020
v5.0.0-alpha2 automation moved this from Approved to Shipped Sep 1, 2020
@jeremyvii jeremyvii deleted the add-default-border-radius-to-mixins branch September 2, 2020 13:10
olsza pushed a commit to olsza/bootstrap that referenced this pull request Oct 3, 2020
* Add default parameters to each border radius mixin

* Add border radius changes to migration guide

Co-authored-by: Jeremy Jackson <jeremy@librarymarket.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
v5.0.0-alpha2
  
Shipped
Development

Successfully merging this pull request may close these issues.

None yet

3 participants