Skip to content

Commit cfea9ab

Browse files
authored
docs: Clarify overrideConfig option (#19370)
1 parent 2b84f66 commit cfea9ab

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/integrate/nodejs-api.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ The `ESLint` constructor takes an `options` object. If you omit the `options` ob
143143
* `options.baseConfig` (`ConfigData | ConfigData[] | null`)<br>
144144
Default is `null`. [Configuration object], extended by all configurations used with this instance. You can use this option to define the default settings that will be used if your configuration files don't configure it.
145145
* `options.overrideConfig` (`ConfigData | ConfigData[] | null`)<br>
146-
Default is `null`. [Configuration object], overrides all configurations used with this instance. You can use this option to define the settings that will be used even if your configuration files configure it.
146+
Default is `null`. [Configuration object], added after any existing configuration and therefore applies after what's contained in your configuration file (if used).
147147
* `options.overrideConfigFile` (`null | true | string`)<br>
148148
Default is `null`. By default, ESLint searches for a configuration file. When this option is set to `true`, ESLint does not search for a configuration file. When this option is set to a `string` value, ESLint does not search for a configuration file, and uses the provided value as the path to the configuration file.
149149
* `options.plugins` (`Record<string, Plugin> | null`)<br>

0 commit comments

Comments
 (0)