-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Expand file tree
/
Copy pathBadParamTag.qhelp
More file actions
38 lines (28 loc) · 943 Bytes
/
BadParamTag.qhelp
File metadata and controls
38 lines (28 loc) · 943 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<!DOCTYPE qhelp PUBLIC
"-//Semmle//qhelp//EN"
"qhelp.dtd">
<qhelp>
<overview>
<p>
JSDoc comments for functions and constructors should use the <code>@param</code> tag to describe the available
parameters. Each <code>@param</code> tag should include both the name of the documented parameter and a
description of its meaning and use. A missing name or description makes the tag much less useful and may
indicate badly maintained code.
</p>
</overview>
<recommendation>
<p>
Add the missing items to the <code>@param</code> tag.
</p>
</recommendation>
<example>
<p>
In the following example, the constructor <code>Message</code> has a JSDoc comment containing two
<code>@param</code> tags for its two parameters, both of which are missing descriptions.
</p>
<sample src="examples/BadParamTag.js" />
</example>
<references>
<li>Use JSDoc: <a href="http://usejsdoc.org/tags-param.html">The @param tag</a>.</li>
</references>
</qhelp>