-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Deprecation warning regarding the order of mixed nested declaration #474
Comments
@julien-deramond is this correct or all of the deprecation warnings on bootstrap main branch are coming for there? If we have warnings coming from rfs, we should fix them here and update the included version in Bootstrap. |
Bootstrap main branch is fixed via twbs/bootstrap#40623 (and will be available with v5.3.4). |
In theory updating sass in this repo to the latest version and running all tests should reveal any warnings. For example I see this here https://github.com/twbs/examples/actions/runs/10684628167/job/29615519708?pr=496
which points to rfs |
SASS is introducing a breaking change regarding the output order of nested SCSS rules: https://sass-lang.com/documentation/breaking-changes/mixed-decls/
To help prepare for this, SASS is outputting some deprecation warnings starting with
1.77.7
. I'm getting multiple warnings fromrfs
related to this issue. The affected areas will likely need to change the order of the declarations to get rid of those warnings and prepare for the breaking change, to ensure the variables will still have the correct order (and thereby, precedence).The text was updated successfully, but these errors were encountered: