Conversation
| :var span, | ||
| )) { | ||
| throw SassException( | ||
| 'A top-level selector may not contain a parent selector with a ' |
There was a problem hiding this comment.
Since we had "&" before, I'm curious why it was removed. Wouldn't it be easier for a user to understand & is the parent selector? Or is it implied that users would know that?
There was a problem hiding this comment.
All Sass exceptions include source span information, and we're careful to ensure that's included in the rendering of the exception everywhere. So this will include a little graphic pointing to the & selector, which means repeating it in prose is less useful than describing it.
pubspec.yaml
Outdated
| @@ -1,5 +1,5 @@ | |||
| name: sass | |||
| version: 1.99.0 | |||
| version: 1.100.0 | |||
There was a problem hiding this comment.
1.99 has not been released yet
There was a problem hiding this comment.
Oh, that's probably my mistake. I suppose we might as well roll this into that, then.
| emitted as-is in the CSS output, where they're interpreted as [the scoping | ||
| root]. | ||
|
|
||
| [the scoping root]: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/Nesting_selector#using_outside_nested_rule |
There was a problem hiding this comment.
How stable are MDN links? I'm wondering if it's better to link the spec
There was a problem hiding this comment.
MDN links are pretty stable, and crucially they're much more friendly to people who are just looking to understand CSS. The spec is written for an audience of browser implementers, so it tends to be much denser.
The previous versions weren't actually released.
3 participants
See sass/sass#4206
See sass/sass-spec#2129