Aleks Hudochenkov

> Can we please get confirmation from multiple people affected by this change (ie actual Blind and low-vision people, who are actual Prettier users), that this actually would help in...

> The selector-pseudo-element-no-unknown rule needs to accept true and false so it can be overridden when extending from a predefined config which has it set to true. Use `null` to...

@ybiquitous I think this issue is not about disabling rules, but documentation of configuration in general. ESLint for every example [shows](https://eslint.org/docs/latest/rules/multiline-comment-style) full config value for a rule. Stylelint docs show...

@vilchik-elena we use [`postcss-value-parser`](https://github.com/TrySound/postcss-value-parser) to parse values of the property for this rule. @evilebottnawi one of developers of this parser.

@joe223 it won't change anything, because there is no extra dependencies or different configuration for different syntaxes.

This are two different suggestions. 1. Allow custom message to be a function. It's a nice idea, but could be rather complex. As every rule has different values it's provides...

I don't understand the usefulness of this feature. > However, it's painful having to modify your config by hand Isn't it the same as modifying CLI command?

It will be confusing for people who use [`--rule`](https://eslint.org/docs/user-guide/command-line-interface#--rule) in ESLint. There `--rule` specify a rule. > One problem with doing it in a standalone tool is having to reimplement...

I see this feature as not something that would benefit majority of our users. Therefore, I think `stylelint-only` is a good solution. As it provides extra functionality for people who...

Thank you for using a template. It's not a bug. From [rule description](https://stylelint.io/user-guide/rules/selector-nested-pattern/): > The selector value will be checked in its entirety. If you'd like to allow for combinators...