Repository navigation
Deprecate scss variables in favour of css #9940
Description
Activity
- addeddesignDesign, UI, UX, etc.Design, UI, UX, etc.
on Jun 20, 2018 - added1. to developAccepted and waiting to be taken care ofAccepted and waiting to be taken care of
on Jun 20, 2018 This one didn't made it to 15 - let's move it to 16.
Reacted by John MolakvoæLet's move it to 17.
27 remaining items
@skjnldsv I would like to push forward with this. Can we declare the scss stuff as deprecated for 22 since we droped IE11? This still gives everyone three years of migration period in theory. So I would like to see this rather sooner than later :)
Reacted by John MolakvoæSure, we can do that for 23 and remove the variables.scss from the default import
server/lib/private/Template/SCSSCacher.php
Line 340 in 0447b53
'@import "variables.scss";' .
Line 31 in 9de329a
printf "\$webroot:''; @import 'functions.scss'; @import 'variables.scss'; @import '${FILE}';" | ./build/bin/node-sass --include-path core/css/ > tests/css/${FILE}.css
'@import "variables.scss";' . Feel free to push forward.
It will throw hard for all scss that uses that.
Then the following step is nuking:- the svg colour api
- the on-the-fly scss compiler and have a dedicated npm/bash step to compile all scss?
@skjnldsv I'm not talking about taking action. I meant to say that we add a formal note about this transition to https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/upgrade-guide.html saying that this mechanism is expected to go away
Sure thing! Please do!
- added4. to releaseReady to be released and/or waiting for tests to finishReady to be released and/or waiting for tests to finishand removed1. to developAccepted and waiting to be taken care ofAccepted and waiting to be taken care of
on Aug 13, 2022 Removed in 25
Following #9723