-
Notifications
You must be signed in to change notification settings - Fork 67
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
[BD-46] fix: fixed border-radius of the card img #2511
[BD-46] fix: fixed border-radius of the card img #2511
Conversation
Thanks for the pull request, @PKulkoRaccoonGang! When this pull request is ready, tag your edX technical lead. |
✅ Deploy Preview for paragon-openedx ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
28ec098
to
38c70c9
Compare
38c70c9
to
954063f
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #2511 +/- ##
=======================================
Coverage 91.65% 91.65%
=======================================
Files 236 236
Lines 4195 4195
Branches 1012 1012
=======================================
Hits 3845 3845
Misses 346 346
Partials 4 4 ☔ View full report in Codecov by Sentry. |
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.
@adamstankiewicz I have checked orientation='horizontal'
+ isLoading
and it seems Skeleton is invisible for Card.Header
and Card.Status
. Also I think that it is good idea to implement isLoading for Card.Body
too.
@@ -41,7 +41,7 @@ $card-logo-bottom-offset-horizontal: .4375rem !default; | |||
$card-logo-width: 7.25rem !default; | |||
$card-logo-height: 4.125rem !default; | |||
|
|||
$card-image-border-radius: .3125rem !default; | |||
$card-image-border-radius: $card-border-radius !default; |
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.
@adamstankiewicz was the intention of this comment to handle things this way, or to just use $card-border-radius
everywhere directly?
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.
In this PR @adamstankiewicz proposed to unify specific border-radius variables for Card and CardImg.
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.
@PKulkoRaccoonGang @brian-smith-tcril I believe it would be preferable to have a single $card-border-radius
used everywhere directly. That said, if we remove $card-image-border-radius
, any brand authors that might have overridden that variable to customize the brand would no longer be able to. That said, it's probably unlikely many brand authors are modifying this variable 🤷♂️
Perhaps we plan to keep it with $card-image-border-radius: $card-border-radius
as currently implemented for now and then remove it fully (in favor of using $card-border-radius
everywhere directly) in the alpha
breaking release?
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!
@PKulkoRaccoonGang 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
🎉 This PR is included in version 20.46.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Fixed border-radius of the Card img
Issue: #2498
Deploy Preview
Card component
Merge Checklist
example
app?wittjeff
andadamstankiewicz
as reviewers on this PR.Post-merge Checklist