Masafumi Koba

> make the error message a parameterless (constant) function, and then pass an empty `[]` into `messageArgs`? The pro here is that we consistently use the same method to create...

@jeddy3 Thanks for summarizing. But I'd like to confirm the rule guideline before implementing a new rule. The guideline says "*A rule must have singular purpose that doesn't overlap with...

@Mouvedia Good point. So how about the following idea? ```js { 'a': 'color', 'b': /color/, 'c': ['color', /position/], 'd': {'color': 'red', 'color': /blue/}, } /* ⬇️ normalized ⬇️ */ {...

@astorije Thanks for the report using the template. I tried reproducing the reported problem but could not reproduce it for some reason. Did I miss something? `package.json`: ```json { "devDependencies":...

@astorije Thanks for the explanation. I confirmed `ignoreFiles` doesn't work when putting a config file in a different folder. I understand the problem. 👍🏼 Currently, `ignoreFiles` behaves as follows: https://github.com/stylelint/stylelint/blob/7f51872f69510042ded354f24f4919de8d03a346/docs/user-guide/configure.md?plain=1#L442-L446...

Related: - #5804

For example, forcing `cwd` might resolve the problem with a JS config, though it's a bit hacky. ```js const cwdGlob = process.cwd().replaceAll("\\", "/"); // unix path style for globs module.exports...

@dhoulb Providing an `ignoreCustomProperties` option sounds good. Could you please open an issue? It'd be helpful if you could describe your motivation in detail.

@silverwind Thanks for the proposal. Could you please comment on a link to the CSS spec you quoted? Also, does this syntax error occur with other at-rules?

@romainmenke Surely, this rule might help people to notice mistakes of `var()` etc. in at-rules. But, I'm concerning about the @silverwind's [comment](https://github.com/stylelint/stylelint/issues/6859#issuecomment-1563330538): > So it seems the spec is not...