@@ -162,37 +162,40 @@ by decreasing precedence:
162
162
<a name =" check-examples-options-for-determining-eslint-rule-applicability-allowinlineconfig-nodefaultexamplerules-matchingfilename-configfile-checkeslintrc-and-baseconfig-rules-disabled-by-default-unless-nodefaultexamplerules-is-set-to-true " ></a >
163
163
### Rules Disabled by Default Unless <code >noDefaultExampleRules</code > is Set to <code >true</code >
164
164
165
- * ` eol-last ` - Insisting that a newline "always" be at the end is less likely
166
- to be desired in sample code as with the code file convention.
165
+ * ` eol-last ` (and ` @stylistic/eol-last ` ) - Insisting that a newline "always"
166
+ be at the end is less likely to be desired in sample code as with the code
167
+ file convention.
167
168
* ` no-console ` - This rule is unlikely to have inadvertent temporary debugging
168
169
within examples.
169
- * ` no-multiple-empty-lines ` - This rule may be problematic for projects which
170
+ * ` no-multiple-empty-lines ` (and ` @stylistic/no-multiple-empty-lines ` ) - This
171
+ rule may be problematic for projects which
170
172
use an initial newline just to start an example. Also, projects may wish to
171
173
use extra lines within examples just for easier illustration
172
174
purposes.
173
175
* ` no-undef ` - Many variables in examples will be ` undefined ` .
174
176
* ` no-unused-vars ` - It is common to define variables for clarity without
175
177
always using them within examples.
176
- * ` padded-blocks ` - It can generally look nicer to pad a little even if one's
177
- code follows more stringency as far as block padding.
178
+ * ` padded-blocks ` (and ` @stylistic/padded-blocks ` ) - It can generally look
179
+ nicer to pad a little even if one's code follows more stringency as far
180
+ as block padding.
178
181
* ` jsdoc/require-file-overview ` - Shouldn't check example for jsdoc blocks.
179
182
* ` jsdoc/require-jsdoc ` - Wouldn't expect jsdoc blocks within jsdoc blocks.
180
183
* ` import/no-unresolved ` - One wouldn't generally expect example paths to
181
184
resolve relative to the current JavaScript file as one would with real code.
182
185
* ` import/unambiguous ` - Snippets in examples are likely too short to always
183
186
include full import/export info.
184
- * ` node/no-missing-import ` - See ` import/no-unresolved ` .
185
- * ` node/no-missing-require ` - See ` import/no-unresolved ` .
187
+ * ` node/no-missing-import ` (and ` n/no-missing-import ` ) - See ` import/no-unresolved ` .
188
+ * ` node/no-missing-require ` (and ` n/no-missing-require ` ) - See ` import/no-unresolved ` .
186
189
187
190
For ` checkDefaults ` , ` checkParams ` , and ` checkProperties ` , the following
188
191
expression-oriented rules will be used by default as well:
189
192
190
- * ` quotes ` - Will insist on "double".
191
- * ` semi ` - Will insist on "never".
193
+ * ` quotes ` (and ` @stylistic/quotes ` ) - Will insist on "double".
194
+ * ` semi ` (and ` @stylistic/semi ` ) - Will insist on "never".
192
195
* ` strict ` - Disabled.
193
196
* ` no-empty-function ` - Disabled.
194
197
* ` no-new ` - Disabled.
195
- * ` no-unused-expressions ` - Disabled.
198
+ * ` no-unused-expressions ` (and ` @typescript-eslint/no-unused-expressions ` ) - Disabled.
196
199
* ` chai-friendly/no-unused-expressions ` - Disabled.
197
200
198
201
<a name =" user-content-check-examples-options-for-determining-eslint-rule-applicability-allowinlineconfig-nodefaultexamplerules-matchingfilename-configfile-checkeslintrc-and-baseconfig-options-for-checking-other-than-example-checkdefaults-checkparams-or-checkproperties " ></a >
0 commit comments