Masafumi Koba

@rakleed Thanks for the proposal. However, the `verbose` formatter shows the info: It may be helpful if the default formatter also shows the same info.

Yeah, this is ready to implement. And your suggestion sounds good to me 👍🏼

@slalomzacharyd Thanks for using the template. I understand your motivation well. But your expectation seems to have been realized. See this [online demo on StackBlitz](https://stackblitz.com/edit/stackblitz-starters-hmplvt?file=test.css). You expect Stylelint doesn't output...

@pamelalozano16 Thanks for the request. That's so interesting to me. To clarify, can you provide a specific example with other tools, please?

@pamelalozano16 Thanks for the info. I understand your request well (although the link to JSLint may be incorrect). 👍🏼 We can probably refer to ESLint, too. It provides the API...

@pamelalozano16 Please let us know your specific use case. What kind of data do you need? Like ESLint, are only `fix.range` and `fix.text` enough?

@romainmenke Nice catch, thank you! I now realize the coverage is not enough. You can work on the `main` branch instead of the `v16` branch if you prefer. 👍🏼

@romainmenke Let me ask how to fix this issue. Do you suggest traversing `calc()` nodes by the tokenizer and parser of `csstools` like this? https://github.com/stylelint/stylelint/blob/f4c75c911275f7c972f285495c6e037c2731981e/lib/rules/function-no-unknown/index.mjs#L61

@romainmenke Thanks for the detailed answer! I'll try to tackle this problem.

This issue is reproduced with the latest version, so I've labeled "ready to implement" back. I'm now working on refactoring this rule. By the way, the inactivity of [`postcss-value-parser`](https://github.com/TrySound/postcss-value-parser) may...