@codacy/tools-eslint-9 0.20.0 → 0.21.0

package/README.md

@@ -67,6 +67,14 @@ pnpm test     # Run tests
   latter duplicating `@stylistic/jsx-sort-props`). Measured on an ordinary React login form,
   tag gating produced 15 findings from rules the project had no reason to enable. Same
   reasoning for the Vue SFC custom-block rules under `jsonc`/`yml`.
+
+  There is **no `webdriverio` key**, even though `plugin-registry.ts` still loads
+  `eslint-plugin-wdio` and ESLint 8's mapping still gates on `ESLint8_wdio_`. Codacy dropped the
+  wdio ruleset from ESLint 9's catalog, so `ESLint9_wdio_` matches nothing upstream and the key
+  was gating patterns that can no longer be selected. `mapping-drift.test.ts` will only catch this
+  once `pnpm prefetch` refreshes `patterns.json` — the committed mirror still lists the three
+  rules. Do not re-add the key without checking the tool's live pattern list first.
+
 - ESLint 9 uses the **flat config** format exclusively. The adapter generates flat config arrays when building from Codacy patterns.
 - Pattern IDs use the same encoding as the codacy-eslint9 wrapper: `_` → `__` then `/` → `_` (encode), reverse for decode. This means `_` in rule names is escaped as `__`.
 - The `blacklist.ts` file contains 30+ rules known to crash ESLint or produce severe false positives, sourced from the codacy-eslint9 wrapper. The `isBlacklisted()` function also checks regex patterns (e.g. `unused-imports/*-ts`).