Masafumi Koba
Masafumi Koba
@RawToaster Thank you for providing the reproducible demo! Indeed, this is a false positive bug due to non-standard JSX syntax. In general, the Stylelint built-in rules must [support standard syntax...
@ryo-manba Thanks for the proposal. This idea sounds great, but some of users may not be pleasant to increase the heavy dependency [`web-features`](https://www.npmjs.com/package/web-features) for just one rule. So first, I'd...
Great! π Besides, it seems better to introduce the new plugin in Awesome Stylelint βΊοΈ
Hi @kaelzhang, There is almost no diff between 5.3.2 and 6.0.2, but is it intentional? Introduced files in 6.0.0, such as `index.mjs`, have been removed in 6.0.2. π€ ```sh-session $...
Got it, sorry for my double comment. I found the following release page describes that, I hope anyone else could notice the helpful info. https://github.com/kaelzhang/node-ignore/releases/tag/6.0.1
Sounds good, but let me confirm: is this rule for rules, not declarations? In the sample CSS code, `a { ... }` not in `@layer {}` seems to be disallowed.
Oh, the example of `a { @layer {...} }` is indeed tricky. I got the naming. ππΌ So, what do you think about the reported ranges? For example, is the...
The reported range sounds good to me. ππΌ The name `declaration-list-nesting-at-rule-required-list` is not so bad, but the doubled "list" seems a bit verbose to me. So, according to the [CSS...
Sounds good. I just fixed the rule name in this issue description. ππΌ
Agree with . I think necessity wins consistency when adding secondary options.