-
Notifications
You must be signed in to change notification settings - Fork 153
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
chore: Fix sass deprecation warnings #2638
Conversation
d8d94d2
to
1c39325
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2638 +/- ##
=======================================
Coverage 96.00% 96.00%
=======================================
Files 749 749
Lines 20896 20896
Branches 7070 7119 +49
=======================================
Hits 20062 20062
Misses 780 780
Partials 54 54 ☔ View full report in Codecov by Sentry. |
1c39325
to
17a8bbd
Compare
17a8bbd
to
d4a0b10
Compare
d4a0b10
to
c0d9785
Compare
c0d9785
to
02fc216
Compare
02fc216
to
1535271
Compare
@@ -78,6 +78,7 @@ function stylesTask(theme) { | |||
designTokensFileName: theme.designTokensOutput, | |||
descriptions, | |||
jsonSchema: true, | |||
failOnDeprecations: true, |
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.
Currently there are zero deprecation warnings. This line is to make sure it the build fails if anybody attempts using deprecated setup
&-disable-paddings { | ||
margin-block: 0; | ||
grid-column: 1 / -1; | ||
@include desktop-only { | ||
grid-column: 2 / span 3; | ||
} | ||
margin-block: 0; | ||
} |
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.
This snippet demonstrates the deprecated pattern very clear. Top level styles should always go first, before any nested rules.
/* | ||
Warning! If these design tokens for width change it will adversely impact | ||
the calculation used to determine the Split Panel maximum width in the | ||
handleSplitPanelMaxWidth function in the context. | ||
*/ |
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.
This comment is copy-paste from VR app layout to the toolbar version, but it is not relevant anymore, because the implementation changed completely
|
||
@include styles.styles-reset; |
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.
I do not know what to say here. Hiding the reset line here is a readability issue, great that the new deprecation forces us to fix this
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.
Thanks for the explanatory comments
1535271
to
845400c
Compare
Before this change, the resizer button was relatively positioned when focused. The relative position was coming from the `focus-highlight` mixin. This regression was introduced when fixing sass deprecation warnings (#2638). Wrapping the absolute position in `& {}` creates a separate rule which takes precedence because of the rule declaration order.
Before this change, the resizer button was relatively positioned when focused. The relative position was coming from the `focus-highlight` mixin. This regression was introduced when fixing sass deprecation warnings (#2638). Wrapping the absolute position in `& {}` creates a separate rule which takes precedence because of the rule declaration order.
Description
Resolves #2571
Related links, issue #, if available: n/a
How has this been tested?
Screenshot tests in my pipeline
Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness
CONTRIBUTING.md
.CONTRIBUTING.md
.Security
checkSafeUrl
function.Testing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.