Richard Hallows

@sw1tch3roo Thank you for taking on another rule! Let's start simple with a strict rule that disallows a single nesting selector anywhere inside a rule or at-rule, e.g.: ```css a...

Holding off on `feature-no-deprecated` SGTM. How do we feel about a `property-no-deprecated` rule? It seems there are [at least a dozen or so](https://stackoverflow.com/a/74980459). I'd be in favour of it.

We've typically split things into multiple rules because our rules start small but tend to balloon as we workaround edge cases. Writing standalone small rules has helped us keep rule...

@mweinand Thank you for the request. Please [open a new issue](https://github.com/stylelint/stylelint/issues/new?template=REQUEST_A_FEATURE.yml) so that we can discuss adding a new `*-list` rule for your use case. You can typically use the...

@ybiquitous Thank you for your review! I've pushed a couple of commits for your suggestions.

If we merge this after https://github.com/stylelint/stylelint/pull/8859, shall we also update the migration guide in this PR with two new headings under "Significant changes"? Something along the lines of: --- ##...

> what if we could refine the naming like this? Those sound good to me; `standard` and `nonstandard` would work well in the context of the [suggested migration guide entry](https://github.com/stylelint/stylelint/pull/8858#issuecomment-3597618504).

@rakleed Thanks for the report. Someone more familiar with the types may chime in to correct me, but I believe `Config` is for the [configuration object](https://stylelint.io/user-guide/configure) and `LinterOptions` is for...

Thank you for continuing to work on implementing standard nesting and for writing up this issue so clearly! > Is this maybe purely because `:not()` was the first such functional...

> and remove the options in future major versions I'm beginning to think we should make a clean break from resolving nesting and supporting non-standard nesting in `17.0.0`. I suspect...