-
Notifications
You must be signed in to change notification settings - Fork 191
[less] css-varvalueexpected when using more complicated variable assignment statements #141
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
Comments
I just noticed #135, tough my understanding of the source code is very limited so i cannot tell if that PR solves this problem |
I can confirm I have same working with less. Just copying examples from here http://lesscss.org/features/#maps-feature it's easy to reproduce. |
Hellow, Same here using multiple guarded namespaces and ref-link them to a variable as shown below. You can copy and paste this code on this online Less compiler (which uses Less 3.9.0), so its valid Less code! @color: light;
#scheme() when (@color = light){
primary: #f0f0f0;
secondary: #000000;
/* [...] */
}
#scheme() when (@color = dark){
primary: #121212;
secondary: #FFFFFF;
/* [...] */
}
@primary: #scheme[primary]; // <-- "scheme" gets an error with css-varvalueexpected!
@secondary: #scheme[secondary]; // <-- It's fine, doesn't get shown as error!
.my-color{
color: @primary;
} Sincerely, |
I tested the cases as written above. All seems to be working with the merging + shipping of #135. Thanks for the effort! |
I am still getting lint warnings for valid CSS code
|
@DATEx2 can you file an new issue? |
|
The following code will compile correctly on
[email protected]
The
#util
part of@var: #util.convert...
will signal acss-varvalueexpected
error as wil the . from@other: .mixin()[]
Might be related to #134
The text was updated successfully, but these errors were encountered: