-
Notifications
You must be signed in to change notification settings - Fork 460
[BUG] Duplicate rule keys in .stylelintrc.json configuration #2771
Copy link
Copy link
Closed
Labels
GSSoC-26Official GSSoC 2026 issueOfficial GSSoC 2026 issueacceptedContribution approved for integration into EaseMotion CSSContribution approved for integration into EaseMotion CSSgood first issueGood for newcomersGood for newcomersgssoc:approvedApproved for GSSoC contributionsApproved for GSSoC contributionshelp wantedExtra attention neededExtra attention neededlevel:intermediateRequires moderate project understandingRequires moderate project understanding
Metadata
Metadata
Assignees
Labels
GSSoC-26Official GSSoC 2026 issueOfficial GSSoC 2026 issueacceptedContribution approved for integration into EaseMotion CSSContribution approved for integration into EaseMotion CSSgood first issueGood for newcomersGood for newcomersgssoc:approvedApproved for GSSoC contributionsApproved for GSSoC contributionshelp wantedExtra attention neededExtra attention neededlevel:intermediateRequires moderate project understandingRequires moderate project understanding
🐛 What's broken?
The
.stylelintrc.jsonfile contains duplicate keys within the"rules"object. Defining the same rule multiple times in a JSON configuration file can cause unpredictable behavior depending on the parser and creates confusion for anyone maintaining the file.Specifically, the following rules are declared more than once:
color-function-alias-notation(both set tonull)no-duplicate-selectors(set tonull, then later set totrue)declaration-block-no-duplicate-properties(set tonull, then later set totrue)📋 Steps to Reproduce
.stylelintrc.json."rules"object.✅ Expected Behavior
Each stylelint rule should only be defined once in the configuration file to ensure the linter enforces the correct and intended value. The duplicate entries should be removed, keeping only the intended final values (e.g.,
truefor the duplication rules).❌ Actual Behavior
Multiple identical keys exist in the same JSON object, violating JSON best practices.
🔗 Reproduction
Current Structure (Duplicates highlighted):