What is the problem you're trying to solve?

Currently, the shorthand-property-no-redundant-values rule triggers a warning when using shorthand with four values (e.g., inset: auto 0 0 0;). This is because the rule considers it redundant, as the fourth value (the left value) can be inferred as 0 with three values. (e.g., inset: auto 0 0;) .

However, in cases where the left value is implicitly 0, many developers prefer the clarity of using four values for better legibility.

What solution would you like to see?

Adding a configuration option (something like allowExplicitLeftValue) that allows four values when the top and bottom values are different (since this would result in a three-value shorthand property).