Add checkContextFunctionalPseudoClasses: [] to selector-max-id

[brigitamaria]

What is the problem you're trying to solve?

I'm using selector-max-id: 0 on a project to disable ID selectors on the CSS files, but something like :global(#foo) is not throwing any errors.

What solution would you like to see?

Currently, :global and :local is not included on isContextFunctionalPseudoClass.
Including those scope selectors in that function will affect another rules which also use the same function, so what do you think about this use case?
I'd be happy to help so let me know about your opinion, thank you!

[jeddy3]

@brigitamaria Thanks for the request and for using the template.

The built-in rules only support standard CSS syntax from the specifications. However, we can discuss adding a includeContextFunctionalPseudoClasses: [] option to the selector-max-* rules.

For example:

{
  "rules": {
    "selector-max-id": [0, {
      "includeContextFunctionalPseudoClasses": ["--custom-pseudo-class"]
    }]
  }
}

The new option would go alongside the existing ignoreContextFunctionalPseudoClasses one.

[Mouvedia]

I found cases that warrants the addition of a new option: :-webkit-any(), :-moz-any().

[brigitamaria]

I like the suggestion for adding a new option, but how should we treat the presedence if we pass the same elements to includeContextFunctionalPseudoClasses and ignoreContextFunctionalPseudoClasses?

[Mouvedia]

but how should we treat the precedence if we pass the same elements to includeContextFunctionalPseudoClasses and ignoreContextFunctionalPseudoClasses?
["/regex/", /regex/, "non-regex"]

I advise against order because it wasn't consistent for objects in ES5.
It's easy to detect conflicts for non-regex and warn.

A simple solution would be to have one of the two have the priority.
e.g. anything set by ignoreContextFunctionalPseudoClasses can be overruled by includeContextFunctionalPseudoClasses

[Mouvedia]

@jeddy3 @ybiquitous it looks warranted, but I may be biased; can we change the status?