Add range context support to media-feature-name-* rules

[jeddy3]

Ref: #1732 (comment)

@media (10px < width > 50px) {}

Is dependent on the creation of a range context parser.

[vankop]

I have look only on tests and did not understand from them that this is not a part of the parser yet 🤦🏼‍♂️

[alexander-akait]

@vankop because parser is not maintainable 😞

[jdiogopeixoto]

I am available to work on this.
Should I change media-feature-name-* rules to not ignore range context medias? It would be necessary to make a workaround, since the parser is not being maintained.

[jeddy3]

I am available to work on this.

Fantastic!

Should I change media-feature-name-* rules to not ignore range context medias?

Yes. If you can adapt the rules to support range context media robustly, then we should no longer ignore them.

[jdiogopeixoto]

Nice, I will start work on this.
I noticed that already exists two rules for ranged operators. Because of that wouldn't it be better to create new rules for each media-feature-name-* instead of adapting the rules? Just for consistency.

[jeddy3]

I will start work on this.

Good stuff.

I noticed that already exists two rules for ranged operators. Because of that wouldn't it be better to create new rules for each media-feature-name-* instead of adapting the rules?

The two rules (media-feature-range-operator-space-after and media-feature-range-operator-space-before) are targeting the range operator within media features, which is a specific bit of punctuation.

Whereas the media-feature-name-* rules are targeting media feature names, which are present:

• outside of the range context
• within the range context

At the moment, the media-feature-name-* rules only check media feature names outside of the range context. It should, however, check all media feature names regardless of the context. To do so would be consistent with our conventions.