-
Notifications
You must be signed in to change notification settings - Fork 235
Fallback for imported variables #3
Comments
isotope-ui relies on the syntax-variables to set the So, I can (and will in a moment) fix it on my end. However, we may need a rule that syntax-variables and ui-variables files stick to the required values, to make them safe for importing. These files being the "API" to pass style across packages might require some strictness here. Anything else should perhaps be moved to a different file. |
@braver I think you can keep it as is and it should be fixed in One. Isotope works for all other themes I tested. It's just that I set it up like this: // colors.less
@syntax-contrast: ...;
@syntax-base-color: ...;
// syntax-variables.less
@import "colors";
@syntax-background-color: darken(@syntax-base-color, @syntax-contrast); Now when Isotope UI tries to use the So as a convention we could say that |
I renamed |
You're right.. the conflict was Ok, closing this for now. But yeah.. we'll have to look into it once the theme settings get added. |
The One Syntax theme breaks when using https://atom.io/themes/isotope-ui.
I think the problem is that Isotope tries to use the
@syntax-background-color
from One, but that one uses a variable imported from another LESS file (color.less), which Isotope does't (and shouldn't) import. https://github.com/atom/one-dark-syntax/blob/master/stylesheets/syntax-variables.less#L17I'll have to look into it more, but maybe as a rule, the "official" syntax variables aren't allowed to be dependant on importing other files.
/cc @braver (no need to change anything in Isotope, just FYI)
The text was updated successfully, but these errors were encountered: