We have a custom theme and make use of CSS customizations using common.scss. It seems to have broken with the recent upgrade, e.g. styles defined in common.scss are not read anymore.
Can you please pinpoint me into any changes I need to make or fix this issue if it is a regression?
I cannot reproduce this. I am running 3.2.0.beta2-dev on two separate instances and the remote common.scss files for themes and components seem to be functioning as expected, as is the common css theme editor. Have you tried narrowing it down by disabling other components? Have you made any changes or added any components lately?
If you want to post a link to the theme repository, I can have a look and test it and perhaps see what the issue might be.
Ok that was really odd and yes it appears that your instance of 3.2.0.beta2-dev has an issue reading private repo files, or at least the common.scss file. As soon as you reverted to beta1, the common.scss file was recognized and the formatting fixed. Something is definitely not working as expected there.
Got it! It showed also up in the admin UI already. I have no idea why I did not see it yesterday morning
Error: “+” and “-” must be surrounded by whitespace in calculations. ╷ 1097 │ width: calc(100%- #{$grid_columns_2_width}); │ ^ ╵ /var/www/discourse/common.scss 1097:19 root stylesheet
Interestingly, this did not pose an issue with the previous version. So something seems to have changed to make scss parsing more strict?
After adding the required whitespace, everything looks great again.
I can’t pinpoint the commit, but our team is currently prioritising making theming more stable and friendly. So these (linting) are probably first steps to ensuring stability.