-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Address Sass global function deprecation warnings #849
base: 2.5-stable
Are you sure you want to change the base?
Address Sass global function deprecation warnings #849
Conversation
Signed-off-by: David Chamberlain <[email protected]>
Deprecation warnings: - Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0. More info and automated migrator: https://sass-lang.com/d/import Migrate to use of '@use', '@forward', and '@include' instead Signed-off-by: David Chamberlain <[email protected]>
Deprecation warnings: - Deprecation Warning [global-builtin]: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0. Use color.adjust instead. - Deprecation Warning [color-functions]: lighten() is deprecated. - Deprecation Warning [color-functions]: darken() is deprecated. Use 'color.adjust' instead to preserve existing behavior Signed-off-by: David Chamberlain <[email protected]>
Hello @chaoscommencer, thank you for submitting this pull request. However, this is a non-backwards compatible change and therefore not within the scope of the 2.x series. However, this change isn't acceptable on the I won't be closing this right away but keeping it in limbo for the distant future. |
No problem; I have notifications on in case you would like assistance with this later. I think I saw a similar pull request open for the master branch already. This one of course only applies to the 2.5-stable branch. Have a good one! |
@ashmaroli I thought we've moved on about the problems of breaking changes on the master branch because they are already there as you mentioned at #815 (comment). |
@UlyssesZh, I used the clause may migrate in the comment you have linked to. However, my concern with going forwards with changes in this branch is not just about breaking changes. That would be acceptable given that If its still not clear, follow the steps below at your end:
|
Deprecation warnings:
Use color.adjust instead.
NOTE: 'color.adjust' is used instead to preserve pre-existing behavior
NOTE: This version of the change requires changes 519c8ee - 2074190 from the pull request addressing use of
@import