Actions
action #162500
opencoordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #157510: [epic] Up-to-date JavaScript stack
Switch to more reliable CSS generation, e.g. using sassc
Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
We need sassc because what we currently use is rubygem-sass and that is seen as obsolete by upstream so we need to switch to a supported solution, see https://sass-lang.com/ruby-sass/
Suggestions¶
- There is already a PR for using sassc: https://github.com/mojolicious/mojo-assetpack/pull/151 Optionally use sassc. There is some discussion ongoing.
- Also consider trying out CSS::Sass which is already used by AssetPack (if installed) and is a wrapper around libsass as well. (I didn't consider it first because I thought there must be a reason why we used a call to a ruby script instead of using a perl module)
- https://sass-lang.com/dart-sass is recommended nowadays but it is not in openSUSE. Check if there are plans to add it
Updated by okurz 6 months ago
- Copied from action #162311: [sporadic] openqa-in-openqa-test fails in openqa_webui due to CSS files not successfully generated size:M added
Actions