You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit aa3fb2b
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/src/use/migrate-to-10.0.0.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ The lists below are ordered roughly by the number of users each change is expect
21
21
-[`eslint:recommended` has been updated](#eslint-recommended)
22
22
-[Jiti < v2.2.0 are no longer supported](#drop-old-jiti)
23
23
-[`eslint-env` comments are reported as errors](#eslint-env-comments)
24
+
-[`func-names` schema is stricter](#func-names)
24
25
25
26
### Breaking changes for plugin developers
26
27
@@ -129,3 +130,21 @@ error: /* eslint-env */ comments are no longer supported at file.js:1:1:
129
130
**To address:** Remove any `eslint-env` comments from your code. If you are still using the old configuration system and need help migrating, check the [migration guide](./configure/migration-guide#eslint-env-configuration-comments).
## <aname="func-names"></a> `func-names` schema is stricter
135
+
136
+
In ESLint v10, the [`func-names`](../rules/func-names) rule schema now disallows extra items in the options array. Previously, configurations that included additional array elements beyond the allowed options were accepted but ignored. Such configurations are now considered invalid.
137
+
138
+
For example, this configuration is now invalid due to the extra element `"foo"`:
0 commit comments