Repository navigation
// style comment support #1149
Description
The stylelint and prettier folks have complained about postcss not supporting // style comments in the selector parser.
I have told them that if they need postcss plugins to support it, must come from postcss first and foremost.
Here's an example of how postcss currently parses the "to-end-of-line" comments.
The AST returned is basically useless. If postcss wants to support this, it will need to add specific handling for it. Possibly with an option that enables it, because it's non-standard syntax.
Activity
ai commentedon May 16, 2018
Do they use
postcss-scssparser? Since//is not part of CSS syntax, we keep parsing//there.The AST Explorer doesn't support postcss-scss (your link contains different csstree parser).
chriseppstein commentedon May 16, 2018
@ai ok thanks for clarifying. Sorry about the confusion. I'm still coming up to speed on how all this fits together.
It does look like stylelint uses
postcss-scssand prettier does too. I wasn't aware these existed so I had been testing against postcss itself.The selector parser tries to be all the syntaxes in one with no mode option, strict setting, or anything else like that. I don't think it's a good idea and would prefer if it was clearly supporting specific syntaxes. Errors are a feature.
Closing this, will track from the selector-parser repo.