Alexandra Ellwood
Alexandra Ellwood
+1 The selector& syntax is really useful for UI widget architectures where classes affecting display of the a widget are set on the outermost DOM element of the widget. For...
Personally I think that supporting `selector&` would be easier for users to understand. Currently the situation is like this: ``` & selector { } // works selector & { }...
Also seeing this and agree with the suggested fix. This fix would help a lot with deprecation warning noise.