-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Can't extend a nested class (concatenated selector) #1597
Comments
although closest to #1539 i don't think it is a duplicate.. same root cause as #1539 though..
is treated as .a followed by a b element, with no space between them quite a hard one to solve, though I guess easier to solve than #1539 |
fair enough, I guess if solving one doesn't solve the other then it makes sense to keep both open. |
Hello again : - ) I'm just writing to hear if theres some updates regarding this issue. I have recently forwarded multiple people this issue, regarding to their LESS question about not beeing able to extend nested/generated classes. Kind regards |
+1 I tried doing the exact same thing: .top{
&-first{
background:black;
&-item{
color:white;
}
}
&-second{
background:green;
&-item:extend(.top-first-item){}
}
} expecting: .top-first {
background: black;
}
.top-first-item,
.top-second-item{
color: white;
}
.top-second {
background: green;
} But got instead: .top-first {
background: black;
}
.top-first-item{
color: white;
}
.top-second {
background: green;
} Soo +1 for this issue and looking forward to a fix! :) Original: http://stackoverflow.com/questions/20091264/less-extend-a-previously-defined-nested-selector |
A lot of people are into BEM these days...
|
I guess the easiest way to fix is in the code handling & to change it to combine the value if there are no combinators between the previous value and the next value, then this would work. patches welcome! |
Hello again. Any updates into this? I havn't been following it for some time, but i find my self not beeing able to extend these dynamic classes a abit too often :( Kind regards, |
Again a +1 from me! Found myself needing to be able to extend a nested dynamic class the other day :)
expected:
|
I've been working on the singlepage project, where each page has it's own less file compiled. Each page has it's own body class, so I can extend concatanated classes and other properties like so: <body class="foo-bar-page"> <body class="bar-baz-page"> In my less files i start from not existing classes .foo-bar { &-page { min-height:100%; #somediv { color : red; } &-holder { display : inline-block; } } } For the other page i can just write: .bar-baz { &:extend(.foo-bar all); } And the output will be: .foo-bar-page, .bar-baz-page { min-height: 100%; } .foo-bar-page #somediv, .bar-baz-page #somediv { color: red; } .foo-bar-page-holder, .bar-baz-page-holder { display: inline-block; } Sure if you need to inherit everything. Less 1.7.0 |
+1! |
Merging to #2200. |
Hello, I know it's now into #2200 BUT 5 years without solution is it outdated ?? |
@guillaume-duchemin Not out-dated. Marked as |
+1 |
+1 |
1 similar comment
+1 |
In case someone comes here with a case like @Johns3n's example, you can always just convert that to the following to "share" rules between BEM classes: .ui {
&__theme {
background-image:url(../images/watermark.gif);
background-position:top left;
&, &--inverted {
background-attachment:fixed;
background-repeat:no-repeat;
}
&--inverted {
background-image:url(../images/watermark--inverted.gif);
background-position:top right;
}
}
} i.e. the key useful "trick" in Less is the |
This would be a great feature as utility classes become even more popular. I was wanting to remove some utility classes from the markup where the sizing was set in stone. It would've been nice to just drop in
|
Heya guys.
I have found an annoying issue, which is pretty basic use of two mechanics:
I cant extend a class i generate by nesting it using "& {}"
Heres my example:
Expected result:
What actually happens:
Imo this is very basic use of two mechanics, and it's not like its generated by some kind of wizard looping mixin.
Looking forward to have this fixed :-)
Kind regards, Dennis
The text was updated successfully, but these errors were encountered: