The no-descending-specificity rule makes absolute sense with traditional ways of writing CSS. As soon as you enter the realm of selectors with unique hashes on the other hand it doesn't anymore.
After having updated to the latest version[9.4.0] of stylelint this rule breaks every lint run. false or "never" as values throw the following error Invalid Option: Unexpected option value "false" for rule "no-descending-specificity".
Please, use issue template next time.
To disabled rule use null value.
Please, use issue template next time.
To disabled rule use
nullvalue.
@hudochenkov This link seems to be broken at the moment.
We removed this page recently. Now the answer lays in line of how to turn on/turn off rule documentation: https://stylelint.io/user-guide/configure#rules
Most helpful comment
Please, use issue template next time.
To disabled rule use
nullvalue.