[SPIKE] Check behaviour of older Sass compilers with CSS custom properties #4926
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes how the
hsl
call is made (as older versions of Sass, including Dart Sass v1.0.0, confuse it with Sass' ownhsl
function).It also adds an update to GitHub actions storing the compiled result for each Sass version we test, so we can peek at what's being generated.
For the purposes of using CSS Custom Properties, looks like everything is in order:
--
are present as expected in the outputvar()
calls