Richard Hallows

@silverwind Thanks for the report and for using the template. I've labelled the issue as ready to implement. Please consider [contributing](https://stylelint.io/contributing) if you have time. There are [steps on how...

I jumped the gun there... The rule checks shorthand overriding longhand: ```css a { background-color: red; background: red; } ``` [Demo](https://stylelint.io/demo/#N4Igxg9gJgpiBcICGACYAdAdilAjJYA1gOYBOEArplALSQA2Ep8KZMMmA3FjvkWZWotSMKN0wBfEABoQAMwCW9GADkkAWziIYADw0AHZQDowAZ1MzwETIuIIQGbCnQhSFZaZctHOHC9hg9EikSAAuCtY0uIxENJgQNKYAFkyhSUjUNPrk+jCkoQCeNBAAbnmkCrCeICgsoW4wPCgSWFKykDYKxABiTOph9gBWptaWsPoWiD7OIKaFyvQKmKFeM0GhMHMu0k0ucwULS6F01raJoRlQwVCrLuubKyCtIBJAA). We don't currently have a rule for checking: ```css...

We can treat this as a false negative of [declaration-block-no-redundant-longhand-properties](https://stylelint.io/user-guide/rules/declaration-block-no-redundant-longhand-properties). In the example, ` background-color: red;` is a redundant longhand property because the value is already being set in a...

@ryo-manba Thank you for the clearly written question. I think we can limit the first PR to addressing simpler cases, as the effort needed to fix the complex cases may...

For multiple selectors, you may want to resolve to: ```css :is(.sidebar, .content) h2 { font-size: 18px; } ``` [Spec](https://drafts.csswg.org/css-nesting/#nest-selector). The resolving implementation used in Stylelint's `no-duplicate-selectors` rule predates the spec....

Hi, I'm one of the maintainers of Stylelint. Let me know if anything on the Stylelint end is blocking landing this, and I'll do my best to unblock it.

@naga1914 Yes, you can thank you. I've labelled the PR as wip. There are [steps on how to add a new rule](https://stylelint.io/developer-guide/rules#add-a-rule) in the Developer guide. You can use: -...

With https://github.com/stylelint/stylelint/issues/8162 in motion, there's an overlap with this rule. It feels like `no-duplicate-selectors` is checking for redundant nesting by proxy. Shall we ignore `& {}` by default in this...

Closing as unlikely an issue with Stylelint itself, but rather with the stylus custom syntax or the order plugin. @gapkukb If you have time, I suggest starting your investigation in...

@Mouvedia, let's keep the "status: ask to implement" label; otherwise, it generates monthly noise for anyone watching the repo.