@@ -199,6 +199,8 @@ Or one may set the targeted tag to an object with a custom `message`, but withou
199
199
}
200
200
```
201
201
202
+ Note that the preferred tags indicated in the ` settings.jsdoc.tagNamePreference `
203
+ map will be assumed to be defined by ` check-tag-names ` .
202
204
203
205
The defaults in ` eslint-plugin-jsdoc ` (for tags which offer
204
206
aliases) are as follows:
@@ -236,24 +238,6 @@ This setting is utilized by the the rule for tag name checking
236
238
- ` require-returns-description `
237
239
- ` require-returns-type `
238
240
239
- ### Additional Tag Names
240
-
241
- Use ` settings.jsdoc.additionalTagNames ` to configure additional, allowed JSDoc
242
- tags in the rule ` check-tag-names ` . The format of the configuration is as follows:
243
-
244
- ``` json
245
- {
246
- "rules" : {},
247
- "settings" : {
248
- "jsdoc" : {
249
- "additionalTagNames" : {
250
- "customTags" : [" define" , " record" ]
251
- }
252
- }
253
- }
254
- }
255
- ```
256
-
257
241
### ` @override ` /` @augments ` /` @extends ` /` @implements ` Without Accompanying ` @param ` /` @description ` /` @example ` /` @returns `
258
242
259
243
The following settings allows the element(s) they reference to be omitted
@@ -325,15 +309,12 @@ but restricted to `@param`. These settings are now deprecated.
325
309
when encountering the discouraged type and, if a type is to be preferred
326
310
in its place, the key ` replacement ` to indicate the type that should be
327
311
used in its place (and which ` fix ` mode can replace) or ` false ` if
328
- forbidding the type. The message string will have the following
329
- substrings with special meaning replaced with their corresponding
330
- value (` {{tagName}} ` , ` {{tagValue}} ` , ` {{badType}} ` , and
331
- ` {{preferredType}} ` (or ` {{replacement}} ` ), noting that the latter is
332
- of no use when one is merely forbidding a type).
333
-
334
- If ` no-undefined-types ` has the option key ` preferredTypesDefined ` set to
335
- ` true ` , the preferred types indicated in the ` settings.jsdoc.preferredTypes `
336
- map will be assumed to be defined.
312
+ forbidding the type. The message string will have the substrings with
313
+ special meaning, ` {{tagName}} ` and ` {{tagValue}} ` , replaced with their
314
+ corresponding value.
315
+
316
+ Note that the preferred types indicated as targets in ` settings.jsdoc.preferredTypes `
317
+ map will be assumed to be defined by ` no-undefined-types ` .
337
318
338
319
See the option of ` check-types ` , ` unifyParentAndChildTypeChecks ` , for
339
320
how the keys of ` preferredTypes ` may have ` <> ` or ` .<> ` (or just ` . ` )
0 commit comments