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.
Description
I've cloned this repo on my machine, after running
bundle install
, I executed the./script/server
command and I've got the same deprecation message described by me in #796 . The only difference is I used the next patch version of ruby:ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux]
in my local minima repo.The cause of the error seems to be the SASS compiler (I guess this version I have in my
Gemfile.lock
:sass-embedded (1.77.8-x86_64-linux-gnu)
), because the deprecation message told me to read this page: https://sass-lang.com/documentation/breaking-changes/mixed-decls/The deprecation message warns the offending line can impact the appearance of a page in the browser when the CSS nesting module will be introduced in the future https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_nesting
Proposal
After reading the deprecation explanation, I took the decision to opt-out by moving both offenders before the nested rule.
Why? Because the caveat / edge case the CSS Working Group took in consideration on this issue: w3c/csswg-drafts#8738 and the example found on the main sass-lang web page linked above are completely different than the case we have in
minima
theme.Note both code snippets have the same property assigned a different value inside the nested rule, and the line below the nested rule.
In our case, the property found below the nested rule is
margin-left
, and the property found inside the nested rule ismargin-right
. So I opted out, instead of opting in by using the&
selector.I don't have a strong opinion here, if you want to opt in, I can change the PR. But I've tested the output on my local host by visually inspecting and using the dev tools to check the right CSS rules are applying correctly by looking at the
a.page-link
element found in _includes/header.html on my browser.Everything looks good with the changes I've made.
I'll copy the content of my
Gemfile.lock
file below:Gemfile.lock