You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plugins typically contain SCSS files from which CSS is generated. Normally the CSS is generated by a developer to test the plugin. Sometimes this does not happen. The CSS is then not the intended one. This occurred for a style change to the Programs tab.
There is a bash utility in this repo called update-css, which generates the CSS from SCSS on a per-plugin basis.
I suggest that part of the build process should be to run update-css. If this is a good idea, then
update-css should be changed to ensure that all plugins are checked if no argument is provided to it
dart scss needs installing in the build environment (as documented in the README)
update-css is run each build (dart scss does not change anything if the css is more recent than the scss).
Plugins typically contain SCSS files from which CSS is generated. Normally the CSS is generated by a developer to test the plugin. Sometimes this does not happen. The CSS is then not the intended one. This occurred for a style change to the Programs tab.
There is a bash utility in this repo called update-css, which generates the CSS from SCSS on a per-plugin basis.
I suggest that part of the build process should be to run update-css. If this is a good idea, then
@dontlaugh is this reasonable?
The text was updated successfully, but these errors were encountered: