Masafumi Koba

Make sense. Let's move this into the standard config repo and continue discussing. Ref: https://github.com/stylelint/stylelint-config-standard/blob/5aa5dd57ac814edd98c656da35f2ccc99a64d433/index.js#L111

Revisit old issues: - https://github.com/stylelint/stylelint/issues/1089 - https://github.com/stylelint/stylelint/issues/4884 - https://github.com/stylelint/stylelint/issues/5863

Just to confirm, are both valid, e.g., `optimizeLegibility` and `optimizelegibility`?

Umm, if we enable `camelCaseSvgKeywords`, the following valid CSS using the [`currentcolor`](https://www.w3.org/TR/css-color-4/#currentcolor-color) keyword will be reported: ```css a { color: currentcolor; /* ^ Expected "currentcolor" to be "currentColor" */ }...

Does the SVG spec support `currentColor`, right?

Umm..., it seems we cannot enable `camelCaseSvgKeywords` until fixing the problem. 🤔

I think we can add `cacheLocation` to #5142. > Should we repurpose this issue or close it? Let's close this issue if nobody responds more.

I also think dropping `declaration-block-no-redundant-longhand-properties` is too much because some may still consider the rule helpful. But I also agree that this rule sometimes requires us to be careful when...

@romainmenke If users want to customize a rule's settings defined in a config like `stylelint-config-standard`, they need to override the settings; then cannot merge them. For example, if we want...

Of course, instead of adjusting `declaration-block-no-redundant-longhand-properties` with the secondary options (e.g., `ignoreLonghands`) in `stylelint-config-standard`, we can handle some special cases, as #7924 does for `transition-behavior`. This way seems straightforward for...