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

chore: Fix sass deprecation warnings #2638

Merged
merged 2 commits into from
Sep 19, 2024
Merged

chore: Fix sass deprecation warnings #2638

merged 2 commits into from
Sep 19, 2024

Conversation

just-boris
Copy link
Member

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

  • Changes include appropriate documentation updates.
  • Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
  • Changes do not include unsupported browser features, see CONTRIBUTING.md.
  • Changes were manually tested for accessibility, see accessibility guidelines.

Security

Testing

  • Changes are covered with new/existing unit tests?
  • Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@just-boris just-boris changed the title Fix sass warning chore: Fix sass deprecation warnings Aug 30, 2024
Copy link

codecov bot commented Aug 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.00%. Comparing base (661b396) to head (845400c).
Report is 2 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

@@ -78,6 +78,7 @@ function stylesTask(theme) {
designTokensFileName: theme.designTokensOutput,
descriptions,
jsonSchema: true,
failOnDeprecations: true,
Copy link
Member Author

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

Comment on lines 155 to 161
&-disable-paddings {
margin-block: 0;
grid-column: 1 / -1;
@include desktop-only {
grid-column: 2 / span 3;
}
margin-block: 0;
}
Copy link
Member Author

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.

Comment on lines -66 to -70
/*
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.
*/
Copy link
Member Author

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

Comment on lines -203 to -204

@include styles.styles-reset;
Copy link
Member Author

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

dpitcock
dpitcock previously approved these changes Sep 18, 2024
Copy link
Contributor

@dpitcock dpitcock left a 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

@just-boris just-boris added this pull request to the merge queue Sep 19, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 19, 2024
@just-boris just-boris added this pull request to the merge queue Sep 19, 2024
Merged via the queue into main with commit ed8cc32 Sep 19, 2024
33 checks passed
@just-boris just-boris deleted the fix-sass-warning branch September 19, 2024 11:20
johannes-weber pushed a commit that referenced this pull request Oct 4, 2024
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.
johannes-weber pushed a commit that referenced this pull request Oct 4, 2024
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.
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.

[Bug]: Theming and nested rules
2 participants