Masafumi Koba

> Should this be moved to _discussions_? This has already the `needs discussion` label, right?

> I was talking about [docs.github.com/en/discussions](https://docs.github.com/en/discussions) We don't run GitHub Discussions since we've managed discussions by the label so far. This will not change in the future.

The problem here is not only specific properties (e.g. `text-decoration-thickness`), but also essentially difficult to handle transformation between longhands and shorthands. If we can't easily resolve the problem, we should...

When seeing the rule's implementation, custom logic for some properties have increased. Such a logic will be more, as new properties are added to CSS. https://github.com/stylelint/stylelint/blob/9afaa08c196626fac36e9f6b8b8db9dc164cc11d/lib/rules/declaration-block-no-redundant-longhand-properties/index.mjs#L28 EDIT: If we had...

> But it does expect users to notice. I fear that most will assume that Stylelint knows best and will get frustrated when they eventually find that Stylelint is breaking...

> At the minimum add `"ignoreLonghands": ["text-decoration-thickness"]`. I think this will not resolve the fundamental problem with this rule. First of all, we should discuss if this rule should be...

Yes, sadly, we cannot bump `html-tags` until `stylelint` becomes a pure ESM package.

@Mouvedia If this issue is incomplete, feel free to reopen. 🙏🏼

@darkgreentree Thanks for opening the discussion. This request seems rare and tricky to me, so I am concerned that this addition might make the codebase more complex than necessary or...

@alSergey Just to clarify, you want a different exit code from `0` if lint problems are only warning, right? ```sh-session $ stylelint error-and-warning.css ... ✖ 2 problems (1 error, 1...