@djangocfg/eslint-config 2.1.540 → 2.1.542

package/base.js

@@ -21,6 +21,25 @@ export const config = [
       "turbo/no-undeclared-env-vars": "warn",
     },
   },
+  {
+    rules: {
+      // A leading underscore is how this repo already writes "deliberately
+      // unused" — an interface method that must keep its signature, a caught
+      // error nobody inspects. `typescript-eslint`'s default knows nothing
+      // about that, so it reported the convention itself as a finding, and in
+      // a package linting with `--max-warnings 0` that made the intended
+      // spelling the failing one.
+      "@typescript-eslint/no-unused-vars": [
+        "warn",
+        {
+          argsIgnorePattern: "^_",
+          varsIgnorePattern: "^_",
+          caughtErrorsIgnorePattern: "^_",
+          destructuredArrayIgnorePattern: "^_",
+        },
+      ],
+    },
+  },
   {
     // Design-system token hygiene: forbid raw Tailwind color-scale classes
     // (bg-amber-500, text-emerald-600, border-red-500/40, …) in className /

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@djangocfg/eslint-config",
-  "version": "2.1.540",
+  "version": "2.1.542",
   "description": "Shared ESLint configurations for Next.js, React, and TypeScript projects with best practices and Prettier integration",
   "keywords": [
     "eslint",

package/react-internal.js

@@ -34,6 +34,12 @@ export const config = [
       ...pluginReactHooks.configs.recommended.rules,
       // React scope no longer necessary with new JSX transform.
       "react/react-in-jsx-scope": "off",
+      // Same reasoning, for TypeScript: `react/prop-types` checks for a runtime
+      // `propTypes` declaration, which is what a props TYPE already is here —
+      // statically, and more completely. Left on, it reports every typed
+      // component in the workspace as unvalidated, which trains readers to
+      // scroll past the lint output rather than read it.
+      "react/prop-types": "off",
     },
   },
 ];