Add ignore: ["next-sibling"] to selector-max-type

[iliyaZelenko]

Which issue, if any, is this issue related to?

Closes #3757

Is there anything in the PR that needs further explanation?

"No, it's self explanatory."

[jeddy3]

@iliyaZelenko Thanks!

I've requested a few changes (some using the new "Suggested change" feature).

[iliyaZelenko]

This is my first time when I've done so much in someone else's repository. It's good that everything went well, I think in the future I will still do something for you.

[jeddy3]

Thanks for making the changes. It's looking good!

I've made three very minor doc tweak suggestions:

• adding backticks around the heading
• removing two empty lines

After that, I think it'll look good to me.

It's good that everything went well, I think in the future I will still do something for you.

Thanks for your contribution! It's appreciated :)

[jeddy3]

Looks good to me, thanks!

[jeddy3]

Does anyone have the time to provide a second review on this?

[jeddy3]

@iliyaZelenko Sorry to trouble you once last time, but would you be able to resolve the conflicts so we can merge this?

[iliyaZelenko]

No problem, it seems nothing complicated.

The tests did not pass, I will try to solve it in the near future.

[jeddy3]

The tests did not pass, I will try to solve it in the near future.

I think we're simply missing the "next-sibling" option in the validator. It looks like it got removed when resolving the conflicts. Adding it back in should see the tests passing again. See:

stylelint/lib/rules/selector-max-type/index.js

Line 38 in 2965800

ignore: ["descendant", "child", "compounded"],

[iliyaZelenko]

@jeddy3 You are right, thank you, did not notice.

Everything is working.

[jeddy3]

Changelog entry added:

• Added: ignore: ["next-sibling"] to selector-max-type (#3832).