You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here _myBlock is an implementation detail that I would like not to publish for my consumers. This is not about minification, this is about encapsulation. I did not find such a feature, and although an underline in the beginning of a file name helps, a native solution would be best.
Possible syntax:
:private .myBlock {
}
The text was updated successfully, but these errors were encountered:
In CSS : uses for pseudo-selectors like :hover. So, they are more like filters. I think :private .myBlock not in CSS philosophy. Maybe we should add at-rule:
@private {
.myBlock {
}
}
But anyway in my opinion it is over-engeniring. You don’t need a class in this example,l, because you can do same without .base:
By "private", do you mean you don't want that CSS class to show up in the stylesheet? Like just copy the styles into any classes that compose it, but don't include it in the final stylesheet?
Here
_myBlock
is an implementation detail that I would like not to publish for my consumers. This is not about minification, this is about encapsulation. I did not find such a feature, and although an underline in the beginning of a file name helps, a native solution would be best.Possible syntax:
The text was updated successfully, but these errors were encountered: