-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set sass variables with css variables to allow easy overrides #4263
Conversation
9cbb6ee
to
1a2f337
Compare
With the SCSS variables the compiler would have thrown in error, I am thinking this might might make the SCSS code less reliable and prone to error. With tailwind classnames and SCSS variables, we get auto-completion and intellisense, here someone would have remember of all the variables. My take would be to define all the variables in Keeps the variables at a single place, avoids big refactor. I think we can remove a lot these variables, but using TailwindCSS classes as well. e.g. NOTE: While the css variables are defined in the |
In the e..g :root {
--font-bold: theme("font.bold.weight")
--gutters: theme("spacing.4")
} |
8490949
to
3f8a0e3
Compare
This reverts commit 1a2f337.
890c77e
to
61af24e
Compare
469d74c
to
d30d84d
Compare
c407bc7
to
c441647
Compare
c441647
to
35b137e
Compare
Good points. I'm now setting the sass variables from css variables that are specified in This will allow people to override almost all settings by setting a css variable in Most of the css variables are colours. I notice that we use the colours directly, e.g. Many other things we can do to improve styling of Hypha, this is one step. |
Fixes #4258
Also clean out unused styling items.
With new dart sass and
@use
instead of@import
it is not possible to override sass variables in a separate file. Using css variabels make it possible again, even easy.Test Steps