Masafumi Koba
Masafumi Koba
In another way, we may add `container-query-no-invalid` like [`media-query-no-invalid`](https://stylelint.io/user-guide/rules/media-query-no-invalid).
I doubt if `function-no-unknown` could support at-rules, not only declarations. To avoid this, adding a new rule like `container-query-no-invalid` sounds reasonable to me. I wonder if there are other cases...
Thanks for the info. Since some functions are already supported in at-rules, adding at-rule support to `function-no-unknown` may be possible. The implementation might be as follows: ```js // .../function-no-unknown/index.mjs import...
@romainmenke Thanks for providing the important perspective. As your examples indicate, If we may enhance checks for `@container` and `@supports` in the future, it seems to make sense to implement...
If `function-no-unknown` would scan at-rules too, Stylelint would emit duplicate lint problems caused by both `function-no-unknown` and `container-no-invalid`, right? If so, I worried this would be against the following rule...
Thanks for the replies. I still lean toward the idea of adding new rules for `@container` and `@supports` instead of adding the at-rules support to `function-no-unknown`. But as @Mouvedia commented,...
By the way, I wonder if we should add `@csstools/css-parser-algorithms` and `@csstools/css-tokenizer` to the following recommendation list: 😃 https://github.com/stylelint/stylelint/blob/cf8479c2424183ff4ff9d6f553606fceda3fb2d1/docs/developer-guide/rules.md?plain=1#L98-L102 Edit: I opened PR #7805 to change the document.
@romainmenke Thanks for opening the discussion. To make sure, this issue discusses how a new property in `Warning` should be constructed for autofix, right? https://github.com/stylelint/stylelint/blob/e95d114e2c57ef0426ab7637d4a9e123a203fce4/types/stylelint/index.d.ts#L493-L515
@romainmenke @Mouvedia Thanks for your responses. I understand this issue is derived from #7192. And, it focuses on a new property for fix ranges that will be added to the...
Sorry, I may not understand **"Multiple ranges"** and **"Extended range"** well. 😓 Can anyone provide a simple TypeScript code to understand both easily?