You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the current Sass codebase, the following deprecation warnings are displayed:
1. Nested Rules and Declarations
DEPRECATION WARNING: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`
Cause: Sass will soon change how it handles declarations following nested rules to align with CSS standards. Suggested Fix:
Move declarations to precede the nested rule if you want to maintain the current behavior.
Alternatively, wrap the declaration in & {} to opt into the new behavior.
2. Deprecated for colors, eg. green() Function
DEPRECATION WARNING: green() is deprecated. Suggestion:
color.channel($color, "green", $space: rgb)
Cause: The green() function is deprecated and will be removed in future versions of Sass. Suggested Fix: Replace eg. green() with color.channel($color, "green", $space: rgb) to achieve the same functionality using the new API.
The text was updated successfully, but these errors were encountered:
We don't really have any sass of our own. Just plain CSS in .scss files. I would guess these warnings relate to Bootstrap's sass and will therefore disappear in some future update.
When running the current Sass codebase, the following deprecation warnings are displayed:
1. Nested Rules and Declarations
Cause: Sass will soon change how it handles declarations following nested rules to align with CSS standards.
Suggested Fix:
2. Deprecated for colors, eg. green() Function
Cause: The green() function is deprecated and will be removed in future versions of Sass.
Suggested Fix: Replace eg. green() with color.channel($color, "green", $space: rgb) to achieve the same functionality using the new API.
The text was updated successfully, but these errors were encountered: