Remove SASS warnings by using color.scale and color.channel functions

[mcslayer]

Done

Change SASS function, which is tagged as deprecated

• lightness to color.channel
• darken, lighten, transparentize to color.scale

Use SASS documentation

QA

• Unfortunately, I don't know how better to show a demo for checking the absence of warnings. But everything should work and not show SASS warnings in the console.

Check if PR is ready for release

If this PR contains Vanilla SCSS code changes, it should contain the following changes to make sure it's ready for the release:

• PR should have one of the following labels to automatically categorise it in release notes:
  • Feature 🎁, Breaking Change 💣, Bug 🐛, Documentation 📝, Maintenance 🔨.
• Vanilla version in package.json should be updated relative to the most recent release, following semver convention:
  • if CSS class names are not changed it can be bugfix release (x.x.X)
  • if CSS class names are changed/added/removed it should be minor version (x.X.0)
  • see the wiki for more details
• Any changes to component class names (new patterns, variants, removed or added features) should be listed on the what's new page.

[webteam-app]

mcslayer is not a collaborator of the repo

[jmuzina]

Hi @mcslayer , thanks for your interest and work!

It looks like there are some small visual changes to .p-strip--suru.

Before and after:

Diff view:

I believe your changes to $color-suru-start and $color-suru-end have changed their evaluated results slightly. I'd suggest taking a look there to make sure the appearance of the component is not changed.

[mcslayer]

Thank you for your review. I apologize for any mistakes in the previous submission. Upon further investigation, I discovered that the issue was related to the color.scale function, which did not accurately convert colors. As a result, I opted to use the color.adjust function instead. I tested various options in the Sass playground, and I can now confirm that the implementation is correct.

[bartaz]

Looks good.

Thanks for your help @mcslayer, these warnings we quite annoying and we were just about to do something about it :)