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

Address Sass global function deprecation warnings #849

Draft
wants to merge 3 commits into
base: 2.5-stable
Choose a base branch
from

Conversation

chaoscommencer
Copy link

@chaoscommencer chaoscommencer commented Feb 22, 2025

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.

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

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]>
@ashmaroli
Copy link
Member

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 master branch as well (as of now) since users on the legacy Ruby Sass (via Jekyll 3.x and jekyll-remote-theme plugin) won't be able to use these changes.

I won't be closing this right away but keeping it in limbo for the distant future.

@ashmaroli ashmaroli marked this pull request as draft February 23, 2025 14:00
@chaoscommencer
Copy link
Author

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!

@UlyssesZh
Copy link

@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).

@ashmaroli
Copy link
Member

@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 master is already at v5.0.0.dev. My concern is about users on Jekyll 3.x consuming this theme via jekyll-remote-theme not being able to continue consuming further changes to master because jekyll-3.x cannot use jekyll-sass-converter-3.x.

If its still not clear, follow the steps below at your end:

  • clone this repository.
  • check out this pull request branch. (accessible at refs/pull/849/head)
  • Edit Gemfile to use jekyll ~> 3.9.
  • Build / serve the site to see if the result is acceptable.
  • Edit Gemfile to include jekyll-sass-converter ~> 3.0.
  • Build / serve the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants