-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
v4: Fix Dart Sass divide
usage
#34386
Conversation
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.
@slavede changed every / 2
to * 0.5
. It would be a no-brainer to at least merge these changes into existing bootstrap v4
divide
usage
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.
RFS should be updated in a separate PR I guess, or at least make sure you're using latest RFS instead of modifying it.
Minor a few unrelated line breaks, this looks great: thanks a lot for your effort ❤️
@@ -10,6 +10,7 @@ | |||
// | |||
// Example usage: change the default blue border and shadow to white for better | |||
// contrast against a dark gray background. | |||
|
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.
Unrelated change
@@ -1,5 +1,6 @@ | |||
// Credit: Nicolas Gallagher and SUIT CSS. | |||
|
|||
|
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.
Unrelated change
@@ -9,6 +9,7 @@ | |||
// Configuration |
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.
RFS is a vendor, please do not edit it directly. It needs to be updated from upstream, see RFS repository.
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.
But it doesn't say inside which exact version of rfs we have here? Should I update the latest? If so, it will pull in a lot more changes to it...this way, it would just fix the warnings...and leave functionality/behavior the same
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.
Leave RFS for now, we'll upgrade it in another PR. @XhmikosR Does this sound right to you?
@ffoodd Yeah, RFS shouldn't be touched for sure. Generally, we should be very careful with this PR. It still has some issues on main, I wouldn't hurry backporting it unless we are 100% sure it's OK. |
Fixed linting issues, removed unrelated changes, and removed RFS in #34571. |
Applied sass-migrator for division deprecation issue. Fixes #34353