Skip to content

Deprecate scss variables in favour of css #9940

Description

@skjnldsv

Following #9723

  • Stop importing the scss variable style on every compilation
  • Throw warning at the user/dev [?]
  • Remove runtime scss compilation in favour of buildtime compilation

Activity

  1. added this to the Netcloud 15 milestone on Jun 20, 2018
  2. self-assigned this
    on Jun 20, 2018
  3. nextcloud-bot commented on Jun 20, 2018

    @nextcloud-bot
    Member

    GitMate.io thinks possibly related issues are #3256 (Scss variables), #1786 (Switching to scss), #5395 (Race condition in SCSS generation), #5356 (Deprecated message lazyLoadPreview()), and #5138 (SCSS not working after reboot).

  4. MorrisJobke commented on Nov 7, 2018

    @MorrisJobke
    Member

    This one didn't made it to 15 - let's move it to 16.

  5. MorrisJobke commented on Feb 25, 2019

    @MorrisJobke
    Member

    Let's move it to 17.

  6. removed this from the Nextcloud 17 milestone on Sep 26, 2019
  7. 27 remaining items

  8. added this to the Nextcloud 23 milestone on May 26, 2021
  9. ChristophWurst commented on Jul 5, 2021

    @ChristophWurst
    Member

    @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 :)

  10. skjnldsv commented on Jul 5, 2021

    @skjnldsv
    MemberAuthor

    Sure, we can do that for 23 and remove the variables.scss from the default import

    '@import "variables.scss";' .

    printf "\$webroot:''; @import 'functions.scss'; @import 'variables.scss'; @import '${FILE}';" | ./build/bin/node-sass --include-path core/css/ > tests/css/${FILE}.css

    Feel free to push forward.
    It will throw hard for all scss that uses that.
    Then the following step is nuking:

    1. the svg colour api
    2. the on-the-fly scss compiler and have a dedicated npm/bash step to compile all scss?
  11. ChristophWurst commented on Jul 5, 2021

    @ChristophWurst
    Member

    @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

  12. skjnldsv commented on Jul 5, 2021

    @skjnldsv
    MemberAuthor

    Sure thing! Please do!

  13. removed their assignment
    on Jul 5, 2021
  14. added
    4. to releaseReady to be released and/or waiting for tests to finish
    and removed
    1. to developAccepted and waiting to be taken care of
    on Aug 13, 2022
  15. skjnldsv commented on Aug 13, 2022

    @skjnldsv
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions