Richard Hallows

That's blog post is a great read. > I start doubting if this issue's flexible shorthand feature is really necessary It's not, especially if we hope to migrate to a...

This feature would benefit these two existing rules: - [`custom-property-no-missing-var-function`](https://stylelint.io/user-guide/rules/list/custom-property-no-missing-var-function) - [`no-unknown-animations`](https://stylelint.io/user-guide/rules/list/no-unknown-animations) And these two proposed rules: - https://github.com/stylelint/stylelint/issues/6361 - https://github.com/stylelint/stylelint/issues/6362 Discussion in https://github.com/stylelint/stylelint/issues/6361.

@morishitter FYI, at stylelint we mainly rely on the following sub-parsers: - [`postcss-selector-parser`](https://github.com/postcss/postcss-selector-parser) - [`postcss-value-parser`](https://github.com/TrySound/postcss-value-parser) - [`postcss-media-query-parser`](https://github.com/dryoma/postcss-media-query-parser)

Now http://stylelint.io/user-guide/rules/media-feature-parentheses-space-inside/

> To me, it seems like the rule shouldn't remove these quotes, SGTM, it seems safer not to remove the outer quotes if there are inner quotes (escaped or otherwise).

We typically reserve that label for bugs that impact a lot of people, i.e. something that'd trigger an immediate release. The issue is pinned for visibility, which I think is...

Yes, the second approach looks promising. @romainmenke It's a boon having your input and involvement in Stylelint. You have a wealth of knowledge about the CSS specifications (e.g. https://github.com/stylelint/stylelint/issues/7359#issuecomment-1837185920) and...

It sounds very promising. To summarise: - a global config property (that supports custom syntaxes) to populate `injectedRoots` - applicable rules, e.g. `no-unknown-animations`, use `injectedRoots` by default - an optional...

> I'd be happy to champion this. Sounds great. Let's make the simple version from https://github.com/stylelint/stylelint/issues/4269#issuecomment-530733054 & https://github.com/stylelint/stylelint/issues/4269#issuecomment-1016412442, i.e. 1. Creates `.stylelintrc.json file` with `{ "extends": ["stylelint-config-standard"] }` 2. Installs...

[Here you go](https://github.com/stylelint/stylelint-create). You should be able to open a pull request directly on the repo. That'll make it easier to review. > have started tinkering with the barebones proof...