eslint-plugin-code-style 1.17.2 → 2.0.0

package/AGENTS.md

@@ -6,7 +6,8 @@ Instructions for AI coding agents working with this codebase.
 
 **eslint-plugin-code-style** is an ESLint plugin providing 79 custom formatting rules (70 auto-fixable, 19 configurable, 9 report-only) for React/JSX projects. It's designed for ESLint v9+ flat config system.
 
-- **Main entry:** `index.js` - Contains all 79 rules in a single file
+- **Source code:** `src/` - Modular rule files organized by category
+- **Built output:** `dist/index.js` - Bundled + minified (generated by esbuild, gitignored)
 - **Type definitions:** `index.d.ts` - TypeScript declarations for IDE support
 - **Recommended configs:** `recommended-configs/` - Ready-to-use ESLint configurations
 - **Test apps:** `_tests_/` - Sample apps for testing rules
@@ -17,8 +18,8 @@ Instructions for AI coding agents working with this codebase.
 |--------|-------------------|-------------|--------|
 | React (JS) | `recommended-configs/react/` | `_tests_/react/` | Available |
 | React + TS + Tailwind | `recommended-configs/react-ts-tw/` | `_tests_/react-ts-tw/` | Available |
-| React + TypeScript | - | - | Coming Soon |
-| React + Tailwind | - | - | Coming Soon |
+| React + TypeScript | `recommended-configs/react-ts/` | `_tests_/react-ts/` | Available |
+| React + Tailwind | `recommended-configs/react-tw/` | `_tests_/react-tw/` | Available |
 
 ### Test Projects & Rule Compatibility
 
@@ -26,16 +27,17 @@ Instructions for AI coding agents working with this codebase.
 
 Each test project in `_tests_/` corresponds to a specific tech stack. Rules should ONLY be added to projects that support them:
 
-| Rule Category | `react/` (JS only) | `react-ts-tw/` (TS + Tailwind) | Future: `react-ts/` | Future: `react-tw/` |
+| Rule Category | `react/` (JS only) | `react-ts-tw/` (TS + Tailwind) | `react-ts/` (TS) | `react-tw/` (TW) |
 |---------------|:------------------:|:------------------------------:|:-------------------:|:-------------------:|
 | **General rules** (arrays, functions, etc.) | ✅ | ✅ | ✅ | ✅ |
 | **JSX/React rules** | ✅ | ✅ | ✅ | ✅ |
 | **TypeScript rules** | ❌ | ✅ | ✅ | ❌ |
 | **Tailwind rules** | ❌ | ✅ | ❌ | ✅ |
 
-**TypeScript-only rules** (71 rules in JS projects, 79 in TS projects):
+**TypeScript-only rules** (70 rules in JS projects, 79 in TS projects):
 - `component-props-inline-type`
 - `enum-format`
+- `enum-type-enforcement`
 - `interface-format`
 - `no-inline-type-definitions`
 - `prop-naming-convention`
@@ -66,7 +68,8 @@ Each test project in `_tests_/` corresponds to a specific tech stack. Rules shou
 ## Build & Test Commands
 
 ```bash
-# No build step required - plain JavaScript ES modules
+# Build (required before testing or publishing)
+npm run build       # Bundles src/ into dist/index.js via esbuild
 
 # Test rules against a test app (e.g., react, react-ts, react-ts-tw)
 cd _tests_/<config-name>
@@ -74,23 +77,43 @@ npm install
 npm run lint        # Check for errors
 npm run lint:fix    # Auto-fix issues
 
-# Publish (from root folder only)
-npm publish
+# Publish (from root folder only — run build first)
+npm run build && npm publish
 ```
 
 ## Code Structure
 
-All rules are defined in `index.js` with this structure:
+Rules are organized in modular source files under `src/`:
 
 ```
-index.js
-├── imports (fs, path, url)
-├── Rule 1 definition (const ruleName = { create(), meta: {} })
-├── Rule 2 definition
-├── ... (79 rules total)
-└── export default { meta: {}, rules: {} }
+src/
+├── index.js                    — Entry point, imports all rules, exports plugin object
+├── utils/
+│   └── tailwind.js             — Tailwind CSS class utilities (shared across classname-* rules)
+└── rules/
+    ├── arrays.js               — 3 rules
+    ├── arrow-functions.js      — 4 rules
+    ├── call-expressions.js     — 6 rules
+    ├── classes.js              — 2 rules
+    ├── comments.js             — 1 rule
+    ├── components.js           — 6 rules
+    ├── control-flow.js         — 8 rules
+    ├── functions.js            — 6 rules
+    ├── hooks.js                — 3 rules
+    ├── imports-exports.js      — 8 rules
+    ├── jsx.js                  — 14 rules
+    ├── objects.js              — 5 rules
+    ├── react.js                — 1 rule
+    ├── spacing.js              — 2 rules
+    ├── strings.js              — 1 rule
+    ├── typescript.js           — 8 rules
+    └── variables.js            — 1 rule
+dist/
+└── index.js                    — Bundled + minified output (generated, gitignored)
 ```
 
+The build step (`npm run build`) uses esbuild to bundle all source files into a single minified `dist/index.js`.
+
 ## Rule Implementation Pattern
 
 Every rule follows this exact structure:
@@ -160,8 +183,10 @@ const ruleName = {
 
 When creating a new rule, ALL of the following files must be updated:
 
-#### 1. `index.js` — Rule Implementation
+#### 1. `src/rules/<category>.js` — Rule Implementation
 
+- [ ] Add rule to the appropriate category file in `src/rules/`
+- [ ] Add the variable name to the file's `export { ... }` block
 - [ ] Add JSDoc comment block with the standard format:
   ```javascript
   /**
@@ -181,7 +206,8 @@ When creating a new rule, ALL of the following files must be updated:
   ```
 - [ ] Add `const ruleName = { create(), meta: {} }` definition
 - [ ] Include `fixable: "code"` or `fixable: "whitespace"` in meta if auto-fixable
-- [ ] Add to `rules` object in default export (keep **alphabetical order**)
+- [ ] Import rule in `src/index.js` and add to `rules` object in default export (keep **alphabetical order**)
+- [ ] Run `npm run build` to regenerate `dist/index.js`
 
 #### 2. `index.d.ts` — TypeScript Types
 
@@ -196,11 +222,10 @@ When creating a new rule, ALL of the following files must be updated:
 
 #### 3. `README.md` — Main Documentation
 
-> ⚠️ **IMPORTANT:** README.md has **four separate sections** that mention rules. When adding or editing a rule, you must update ALL relevant sections:
-> - **Rule counts** (6 locations) — must match actual rule count
+> ⚠️ **IMPORTANT:** README.md has **three separate sections** that mention rules. When adding or editing a rule, you must update ALL relevant sections:
+> - **Rule counts** (5 locations) — must match actual rule count
 > - **Quick Start example** (~line 184) — alphabetically sorted configuration example
 > - **Rules Summary table** — brief description with emoji indicators
-> - **Detailed documentation** — full examples, options, and explanations
 >
 > Missing any section will leave documentation inconsistent. Use the `audit-docs` skill to verify all sections are in sync.
 
@@ -208,9 +233,8 @@ When creating a new rule, ALL of the following files must be updated:
 - [ ] Line ~22: `*XX rules (YY auto-fixable)*`
 - [ ] Line ~30: `**XX custom rules** (YY auto-fixable)`
 - [ ] Line ~39: `YY of XX rules support auto-fix`
-- [ ] Line ~100: `**YY rules** support automatic fixing`
-- [ ] Line ~254: `**XX rules total** — YY with auto-fix`
-- [ ] Line ~3037: `YY of XX rules support auto-fixing`
+- [ ] Line ~272: `**XX rules total** — YY with auto-fix`
+- [ ] Line ~409: `YY of XX rules support auto-fixing`
 
 **b) Add rule to Quick Start example** (~line 184, alphabetically sorted):
 ```javascript
@@ -224,7 +248,10 @@ When creating a new rule, ALL of the following files must be updated:
 - Add 🔧 emoji if auto-fixable
 - Add ⚙️ emoji if has configurable options
 
-**d) Add detailed rule documentation section** (in appropriate category section):
+#### 3b. `docs/rules/<category>.md` — Detailed Rule Documentation
+
+Add detailed rule documentation to the appropriate category file in `docs/rules/`:
+
 ```markdown
 ### `new-rule-name`
 
@@ -367,12 +394,12 @@ Run these commands to verify all rules are in sync:
 
 ```bash
 # Count rules in each location
-grep -c "^const [a-zA-Z]* = {$" index.js
+grep -rc "^const [a-zA-Z]* = {$" src/rules/
 grep -c 'code-style/' index.d.ts
 grep -c '"code-style/' recommended-configs/react-ts-tw/eslint.config.js
 
 # Find rules missing from README
-grep -oE '"[a-z-]+":' index.js | tr -d '":' | sort > /tmp/a.txt
+grep -oE '"[a-z-]+":' src/index.js | tr -d '":' | sort > /tmp/a.txt
 grep -oE '\`[a-z-]+\`' README.md | tr -d '\`' | sort | uniq > /tmp/b.txt
 comm -23 /tmp/a.txt /tmp/b.txt
 ```
@@ -383,20 +410,21 @@ comm -23 /tmp/a.txt /tmp/b.txt
 
 **IMPORTANT:** Removing a rule is a **BREAKING CHANGE** requiring a **MAJOR version bump** (e.g., 1.6.0 → 2.0.0).
 
-#### 1. `index.js`
-- [ ] Remove the rule's JSDoc comment block
-- [ ] Remove the `const ruleName = { ... }` definition
-- [ ] Remove from `rules` object in default export
+#### 1. `src/rules/<category>.js` + `src/index.js`
+- [ ] Remove the rule's JSDoc comment block and `const` definition from category file
+- [ ] Remove from the file's `export { ... }` block
+- [ ] Remove import and `rules` object entry from `src/index.js`
+- [ ] Run `npm run build` to regenerate `dist/index.js`
 
 #### 2. `index.d.ts`
 - [ ] Remove from `RuleNames` type union
 - [ ] Remove from `PluginRules` interface
 
-#### 3. `README.md` (all four sections)
+#### 3. `README.md` + `docs/rules/`
 - [ ] Update all rule counts (see [Rule Count Locations](#rule-count-locations))
 - [ ] Remove from `rules: {}` example in Quick Start
 - [ ] Remove from Rules Summary table
-- [ ] Remove detailed documentation section
+- [ ] Remove detailed documentation from `docs/rules/<category>.md`
 
 #### 4. `AGENTS.md`
 - [ ] Update all rule counts
@@ -423,29 +451,29 @@ comm -23 /tmp/a.txt /tmp/b.txt
 
 When modifying an existing rule, check if these need updates:
 
-> ⚠️ **README.md Reminder:** If the rule's behavior, examples, or options change, remember that README.md has multiple sections to update (Quick Start example, Rules Summary table, detailed documentation). See the note in "Adding a New Rule" section for details.
+> ⚠️ **Documentation Reminder:** If the rule's behavior, examples, or options change, update README.md (Quick Start example, Rules Summary table) and the detailed docs in `docs/rules/<category>.md`. See the note in "Adding a New Rule" section for details.
 
 #### If fixing a bug (PATCH version: x.x.+1):
-- [ ] Fix the issue in rule's `create()` function in `index.js`
+- [ ] Fix the issue in rule's `create()` function in `src/rules/<category>.js`
 - [ ] Test in `_tests_/` apps with `npm run lint` and `npm run lint:fix`
 - [ ] Commit: `fix: description of what was fixed in rule-name`
 
 #### If changing rule behavior (PATCH or MINOR depending on scope):
-- [ ] Update rule logic in `index.js`
-- [ ] Update JSDoc in `index.js` (Good/Bad examples if they changed)
+- [ ] Update rule logic in `src/rules/<category>.js`
+- [ ] Update JSDoc in source file (Good/Bad examples if they changed)
 - [ ] Update `README.md` rule documentation section:
   - Update "What it does" if behavior changed
   - Update code examples (✅ Good / ❌ Bad) to reflect new behavior
 - [ ] Test in `_tests_/` apps with `npm run lint` and `npm run lint:fix`
 
 #### If adding new options (MINOR version: x.+1.0):
-- [ ] Add option to `schema` in rule's `meta` object in `index.js`
+- [ ] Add option to `schema` in rule's `meta` object in `src/rules/<category>.js`
 - [ ] Add option handling in `create()` function with default value:
   ```javascript
   const options = context.options[0] || {};
   const newOption = options.newOption !== undefined ? options.newOption : defaultValue;
   ```
-- [ ] Update JSDoc Options section in `index.js`
+- [ ] Update JSDoc Options section in source file
 - [ ] Update README.md rule documentation:
   - Add row to Options table
   - Add configuration example showing the new option
@@ -466,7 +494,7 @@ When modifying an existing rule, check if these need updates:
 
 #### If changing default values (MAJOR version: +1.0.0 — breaking change):
 - [ ] Update default value in `create()` function
-- [ ] Update JSDoc in `index.js`
+- [ ] Update JSDoc in source file
 - [ ] Update README.md options table (Default column)
 - [ ] Commit with `!`: `feat!: change default value for rule-name option`
 
@@ -526,9 +554,9 @@ See "When to Bump Version & Create Tag" section in Git Workflow for details.
 
 ---
 
-### Rule Documentation Format in README.md
+### Rule Documentation Format in docs/rules/
 
-Each rule should have this format in the Rules Reference section:
+Each rule should have this format in its category file under `docs/rules/`:
 
 ```markdown
 ### `rule-name`
@@ -638,7 +666,7 @@ if (node.parent?.type === "CallExpression") return;
 
 ## Rule Categories
 
-Rules are organized in these categories (alphabetically sorted in index.js and README.md):
+Rules are organized in these categories (alphabetically sorted in src/index.js and README.md):
 
 - **Array Rules** — Rules for array formatting
   - `array-callback-destructure`, `array-items-per-line`, `array-objects-on-new-lines`
@@ -687,8 +715,9 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 
 ## Documentation Files
 
-- `README.md` - Main documentation with all 79 rules
-- `recommended-configs/<config-name>/README.md` - Config-specific documentation (references main README for rule details)
+- `README.md` - Main documentation with rule overview and links
+- `docs/rules/` - Detailed rule documentation (17 category files with examples and options)
+- `recommended-configs/<config-name>/README.md` - Config-specific documentation (references docs/rules/ for rule details)
 - `index.d.ts` - TypeScript types for IDE autocomplete
 
 ## Important Notes
@@ -725,12 +754,12 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 | `README.md` | ~22 | `*79 rules (70 auto-fixable, 19 configurable)*` |
 | `README.md` | ~30 | `**79 custom rules** (70 auto-fixable, 19 configurable)` |
 | `README.md` | ~39 | `70 of 79 rules support auto-fix` |
-| `README.md` | ~100 | `**70 rules** support automatic fixing. **19 rules** have configurable options` |
-| `README.md` | ~266 | `**79 rules total** — 70 with auto-fix, 19 configurable` |
-| `README.md` | ~3650 | `70 of 79 rules support auto-fixing` |
+| `README.md` | ~272 | `**79 rules total** — 70 with auto-fix, 19 configurable` |
+| `README.md` | ~409 | `70 of 79 rules support auto-fixing` |
+| `docs/rules/README.md` | ~3 | `**79 rules total** — 70 with auto-fix, 19 configurable` |
 | `AGENTS.md` | ~7 | `79 custom formatting rules (70 auto-fixable, 19 configurable, 9 report-only)` |
 | `AGENTS.md` | ~9 | `Contains all 79 rules` |
-| `AGENTS.md` | ~36 | `(71 rules in JS projects, 79 in TS projects)` |
+| `AGENTS.md` | ~36 | `(70 rules in JS projects, 79 in TS projects)` |
 | `AGENTS.md` | ~89 | `(79 rules total)` |
 | `AGENTS.md` | ~675 | `all 79 rules` |
 | `AGENTS.md` | ~697 | `70 auto-fixable rules, 19 configurable rules, 9 report-only` |
@@ -742,13 +771,13 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 
 ```bash
 # Count total rules
-grep -c "^const [a-zA-Z]* = {$" index.js
+grep -rc "^const [a-zA-Z]* = {$" src/rules/
 
 # Count auto-fixable (code)
-grep -c 'fixable: "code"' index.js
+grep -rc 'fixable: "code"' src/rules/
 
 # Count auto-fixable (whitespace)
-grep -c 'fixable: "whitespace"' index.js
+grep -rc 'fixable: "whitespace"' src/rules/
 
 # Count configurable rules (rules with ⚙️ in README table)
 grep "| \`" README.md | grep -c "⚙️"
@@ -1220,7 +1249,7 @@ This project includes reusable skills in the `.skills/` directory following the
 | `manage-rule` | Add, edit, or remove an ESLint rule with all required file updates |
 | `review-config` | Review a recommended ESLint configuration |
 | `test-rule` | Test an ESLint rule after creating or modifying it |
-| `validate-types` | Verify TypeScript definitions match rules in index.js |
+| `validate-types` | Verify TypeScript definitions match rules in src/index.js |
 
 See `.skills/*/skill.md` for detailed instructions.
 
@@ -1240,7 +1269,7 @@ Test an ESLint rule to verify it works correctly.
 
 **Steps:**
 
-1. **Find the rule** in `index.js` and understand what it checks
+1. **Find the rule** in `src/rules/<category>.js` and understand what it checks
 2. **Identify test app** — Use `_tests_/react/` for JS rules or `_tests_/react-ts-tw/` for TS rules
 3. **Create test cases** in the test app:
    - Add code that should PASS (no violations)
@@ -1260,15 +1289,15 @@ Test an ESLint rule to verify it works correctly.
 
 ### Workflow: Validate Types
 
-Verify TypeScript definitions match the rules in `index.js`.
+Verify TypeScript definitions match the rules in `src/index.js`.
 
 **When to use:** After adding new rules or before releases.
 
 **Steps:**
 
-1. **Count rules in index.js:**
+1. **Count rules in src/:**
    ```bash
-   grep -c "^const .* = {$" index.js
+   grep -rc "^const .* = {$" src/rules/
    ```
    Or count entries in the `rules` export object.
 
@@ -1277,8 +1306,8 @@ Verify TypeScript definitions match the rules in `index.js`.
    - Verify `PluginRules` interface includes all rules
 
 3. **Look for mismatches:**
-   - Rules in `index.js` missing from `index.d.ts`?
-   - Rules in `index.d.ts` that don't exist in `index.js`?
+   - Rules in `src/index.js` missing from `index.d.ts`?
+   - Rules in `index.d.ts` that don't exist in `src/index.js`?
 
 4. **Report:**
    - Total rules: X
@@ -1334,7 +1363,7 @@ Verify documentation accuracy across all files.
 
 1. **Count actual rules:**
    ```bash
-   grep -c "^const .* = {$" index.js
+   grep -rc "^const .* = {$" src/rules/
    ```
 
 2. **Check rule count references:**

package/CHANGELOG.md

@@ -7,6 +7,111 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [2.0.0] - 2026-02-09
+
+**Modular Source Architecture + Minified Build**
+
+**Version Range:** v1.20.0 → v2.0.0
+
+### Changed
+
+- **BREAKING: Modular source architecture** — Split monolithic 23K-line `index.js` into `src/` with 17 category files + shared utilities
+  - `src/index.js` — Entry point importing all rules
+  - `src/rules/*.js` — 17 category files (arrays, arrow-functions, call-expressions, classes, comments, components, control-flow, functions, hooks, imports-exports, jsx, objects, react, spacing, strings, typescript, variables)
+  - `src/utils/tailwind.js` — Shared Tailwind CSS class utilities
+- **Build system** — Added esbuild to bundle and minify `src/` into `dist/index.js`
+  - `npm run build` generates the bundled output
+  - Output is ~269 KB (was ~1 MB), a 73% reduction
+- **Package entry point** — `main` and `exports` now point to `dist/index.js` instead of `index.js`
+- **npm package** — Publishes `dist/index.js` instead of root `index.js`; removed root `index.js` from package
+
+### Added
+
+- `esbuild.config.js` — Build configuration
+- `esbuild` as devDependency
+- `npm run build` script
+
+### Stats
+
+- Total Rules: 79
+- Auto-fixable: 70 rules 🔧
+- Configurable: 19 rules ⚙️
+- Report-only: 9 rules
+- Unpacked size: ~400 KB (was ~1.26 MB)
+
+**Full Changelog:** [v1.20.0...v2.0.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.20.0...v2.0.0)
+
+---
+
+## [1.20.0] - 2026-02-09
+
+**README Reorganization — Split Rules Reference into docs/rules/**
+
+**Version Range:** v1.19.0 → v1.20.0
+
+### Added
+
+- **Rules Reference Documentation** (`docs/rules/`) — 17 category files with detailed rule documentation, examples, and configuration options
+  - `arrays.md`, `arrow-functions.md`, `call-expressions.md`, `classes.md`, `comments.md`, `components.md`, `control-flow.md`, `functions.md`, `hooks.md`, `imports-exports.md`, `jsx.md`, `objects.md`, `react.md`, `spacing.md`, `strings.md`, `typescript.md`, `variables.md`
+- **Rules index page** (`docs/rules/README.md`) — Overview table linking to all 17 category files
+
+### Changed
+
+- **README.md** — Reorganized from ~4,150 lines to ~475 lines by moving detailed rule documentation to `docs/rules/`
+  - Kept: badges, Why This Plugin, Recommended Configs, Features, Installation, Quick Start, Enable All Rules, Rules Summary table, Rules Reference links, Auto-fixing, Disabling Rules, Contributing, License
+  - Moved: All detailed rule examples, options, and explanations to `docs/rules/` category files
+- **Recommended config READMEs** — Updated rule documentation links to point to `docs/rules/` instead of main README
+- **AGENTS.md** — Updated documentation references to reflect new `docs/rules/` structure
+- **package.json** — Added `docs/` to npm `files` array
+
+**Full Changelog:** [v1.19.0...v1.20.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.19.0...v1.20.0)
+
+---
+
+## [1.19.0] - 2026-02-09
+
+**New: React + Tailwind Test Project & Recommended Config**
+
+**Version Range:** v1.18.0 → v1.19.0
+
+### Added
+
+- **React + Tailwind test project** (`_tests_/react-tw/`) — React + Tailwind CSS project (no TypeScript) with 70 code-style rules enabled and Tailwind CSS v4 plugin
+- **React + Tailwind recommended config** (`recommended-configs/react-tw/`) — Ready-to-use ESLint flat config for React + Tailwind CSS projects without TypeScript
+  - Includes 70 JavaScript-compatible code-style rules, Tailwind CSS plugin, and recommended third-party plugins
+  - Documented with installation instructions, rule explanations, and customization guide
+
+### Changed
+
+- Updated Available Configurations table in README.md — React + Tailwind now links to config instead of "Coming Soon"
+- Updated AGENTS.md — React + Tailwind marked as Available with folder paths
+
+**Full Changelog:** [v1.18.0...v1.19.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.18.0...v1.19.0)
+
+---
+
+## [1.18.0] - 2026-02-09
+
+**New: React + TypeScript Test Project & Recommended Config**
+
+**Version Range:** v1.17.2 → v1.18.0
+
+### Added
+
+- **React + TypeScript test project** (`_tests_/react-ts/`) — React + TypeScript project (no Tailwind) with all 79 code-style rules enabled and @typescript-eslint parser
+- **React + TypeScript recommended config** (`recommended-configs/react-ts/`) — Ready-to-use ESLint flat config for React + TypeScript projects without Tailwind CSS
+  - Includes all 79 code-style rules, TypeScript parser, and recommended third-party plugins
+  - Documented with installation instructions, rule explanations, and customization guide
+
+### Changed
+
+- Updated Available Configurations table in README.md — React + TypeScript now links to config instead of "Coming Soon"
+- Updated AGENTS.md — React + TypeScript marked as Available with folder paths
+
+**Full Changelog:** [v1.17.2...v1.18.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.17.2...v1.18.0)
+
+---
+
 ## [1.17.2] - 2026-02-09
 
 **Fix: CamelCase Naming Auto-Fix & Prefix Enforcement**
@@ -1841,6 +1946,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+[2.0.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.20.0...v2.0.0
+[1.20.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.19.0...v1.20.0
+[1.19.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.18.0...v1.19.0
+[1.18.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.17.2...v1.18.0
 [1.17.2]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.17.1...v1.17.2
 [1.17.1]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.17.0...v1.17.1
 [1.17.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.16.0...v1.17.0