eslint-plugin-jsdoc
JSDoc linting rules for ESLint.
Reference to jscs-jsdoc
This table maps the rules between eslint-plugin-jsdoc
and jscs-jsdoc
.
Installation
Install ESLint either locally or globally.
npm install eslint
If you have installed ESLint
globally, you have to install JSDoc plugin globally too. Otherwise, install it locally.
npm install eslint-plugin-jsdoc
Configuration
Add plugins
section and specify eslint-plugin-jsdoc
as a plugin.
{
"plugins": [
"jsdoc"
]
}
Finally, enable all of the rules that you would like to use.
{
"rules": {
"jsdoc/check-examples": 1,
"jsdoc/check-param-names": 1,
"jsdoc/check-tag-names": 1,
"jsdoc/check-types": 1,
"jsdoc/newline-after-description": 1,
"jsdoc/no-undefined-types": 1,
"jsdoc/require-description": 1,
"jsdoc/require-description-complete-sentence": 1,
"jsdoc/require-example": 1,
"jsdoc/require-hyphen-before-param-description": 1,
"jsdoc/require-param": 1,
"jsdoc/require-param-description": 1,
"jsdoc/require-param-name": 1,
"jsdoc/require-param-type": 1,
"jsdoc/require-returns": 1,
"jsdoc/require-returns-description": 1,
"jsdoc/require-returns-type": 1,
"jsdoc/valid-types": 1
}
}
Settings
Alias Preference
Use settings.jsdoc.tagNamePreference
to configure a preferred alias name for a JSDoc tag. The format of the configuration is: <primary tag name>: <preferred alias name>
, e.g.
{
"rules": {},
"settings": {
"jsdoc": {
"tagNamePreference": {
"param": "arg",
"returns": "return"
}
}
}
}
Additional Tag Names
Use settings.jsdoc.additionalTagNames
to configure additional, allowed JSDoc tags. The format of the configuration is as follows:
{
"rules": {},
"settings": {
"jsdoc": {
"additionalTagNames": {
"customTags": ["define", "extends", "record"]
}
}
}
}
Allow @override
Without Accompanying @param
Tags
Use any of the following settings to override require-param
and allow
@param
to be omitted when the specified tags are present on the JSDoc
comment or the parent class comment. The default value for each is false
.
settings.jsdoc.allowOverrideWithoutParam
- Enables behavior with
@override
tagsettings.jsdoc.allowImplementsWithoutParam
- Enables behavior with
@implements
tagsettings.jsdoc.allowAugmentsExtendsWithoutParam
- Enables behavior with
@augments
tag or its synonym @extends
The format of the configuration is as follows:
{
"rules": {},
"settings": {
"jsdoc": {
"allowOverrideWithoutParam": true,
"allowImplementsWithoutParam": true,
"allowAugmentsExtendsWithoutParam": true
}
}
}
Settings to Configure check-examples
The settings below all impact the check-examples
rule and default to
no-op/false except as noted.
JSDoc specs use of an optional <caption>
element at the beginning of
@example
. The following setting requires its use.
settings.jsdoc.captionRequired
- Require <caption>
at beginning
of any @example
JSDoc does not specify a formal means for delimiting code blocks within
@example
(it uses generic syntax highlighting techniques for its own
syntax highlighting). The following settings determine whether a given
@example
tag will have the check-examples
checks applied to it:
settings.jsdoc.exampleCodeRegex
- Regex which whitelists lintable
examples. If a parenthetical group is used, the first one will be used,
so you may wish to use (?:...)
groups where you do not wish the
first such group treated as one to include. If no parenthetical group
exists or matches, the whole matching expression will be used.
An example might be "^```(?:js|javascript)([\\s\\S]*)```$"
to only match explicitly fenced JavaScript blocks.settings.jsdoc.rejectExampleCodeRegex
- Regex blacklist which rejects
non-lintable examples (has priority over exampleCodeRegex
). An example
might be "^`"
to avoid linting fenced blocks which may indicate
a non-JavaScript language.
If neither is in use, all examples will be matched. Note also that even if
settings.jsdoc.captionRequired
is not set, any initial <caption>
will be stripped out before doing the regex matching.
The following settings determine which individual ESLint rules will be
applied to the JavaScript found within the @example
tags (as determined
to be applicable by the above regex settings). They are ordered by
decreasing precedence:
settings.jsdoc.allowInlineConfig
- If not set to false
, will allow
inline config within the @example
to override other config. Defaults
to true
.settings.jsdoc.noDefaultExampleRules
- Setting to true
will disable the
default rules which are expected to be troublesome for most documentation
use. See the section below for the specific default rules.settings.jsdoc.matchingFileName
- Setting for a dummy file name to trigger
specific rules defined in one's config; usable with ESLint .eslintrc.*
overrides
-> files
globs, to apply a desired subset of rules with
@example
(besides allowing for rules specific to examples, this setting
can be useful for enabling reuse of the same rules within @example
as
with JavaScript Markdown lintable by
other plugins, e.g.,
if one sets matchingFileName
to dummy.md
so that @example
rules will
follow one's Markdown rules).settings.jsdoc.configFile
- A config file. Corresponds to ESLint's -c
.settings.jsdoc.eslintrcForExamples
- Defaults to true
in adding rules
based on an .eslintrc.*
file. Setting to false
corresponds to
ESLint's --no-eslintrc
.settings.jsdoc.baseConfig
- An object of rules with the same schema
as .eslintrc.*
for defaults
Finally, the following rule pertains to inline disable directives:
settings.jsdoc.reportUnusedDisableDirectives
- If not set to false
,
this will report disabled directives which are not used (and thus not
needed). Defaults to true
. Corresponds to ESLint's
--report-unused-disable-directives
.
Rules Disabled by Default Unless noDefaultExampleRules
is Set to true
eol-last
- Insisting that a newline "always" be at the end is less likely
to be desired in sample code as with the code file conventionno-console
- Unlikely to have inadvertent temporary debugging within
examplesno-undef
- Many variables in examples will be undefined
.no-unused-vars
- It is common to define variables for clarity without always
using them within examples.padded-blocks
- It can generally look nicer to pad a little even if one's
code follows more stringency as far as block padding.import/no-unresolved
- One wouldn't generally expect example paths to
resolve relative to the current JavaScript file as one would with real code.import/unambiguous
- Snippets in examples are likely too short to always
include full import/export infonode/no-missing-import
- See import/no-unresolved
node/no-missing-require
- See import/no-unresolved
Rules
check-examples
Ensures that (JavaScript) examples within JSDoc adhere to ESLint rules.
Works in conjunction with the following settings:
captionRequired
exampleCodeRegex
rejectExampleCodeRegex
allowInlineConfig
- Defaults to true
noDefaultExampleRules
matchingFileName
configFile
eslintrcForExamples
- Defaults to true
baseConfig
reportUnusedDisableDirectives
- Defaults to true
Inline ESLint config within @example
JavaScript is allowed, though the
disabling of ESLint directives which are not needed by the resolved rules
will be reported as with the ESLint --report-unused-disable-directives
command.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux2 () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {}
function quux () {}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {}
function quux () {}
check-param-names
Ensures that parameter names in JSDoc match those in the function declaration.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux (foo = 'FOO') {
}
function quux (foo = 'FOO') {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (bar, foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar) {
}
function quux (...args) {
}
function quux ({a, b}) {
}
function quux ({a, b} = {}) {
}
function quux ([a, b] = []) {
}
function assign (employees) {
};
Deconstructing Function Parameter
eslint-plugin-jsdoc
does not validate names of parameters in function deconstruction, e.g.
function quux ({
a,
b
}) {
}
{a, b}
is an ObjectPattern
AST type and does not have a name. Therefore, the associated parameter in JSDoc block can have any name.
Likewise for the pattern [a, b]
which is an ArrayPattern
.
check-tag-names
Reports invalid block tag names.
Valid JSDoc 3 Block Tags are:
abstract
access
alias
augments
author
borrows
callback
class
classdesc
constant
constructs
copyright
default
deprecated
description
enum
event
example
exports
external
file
fires
function
global
ignore
implements
inheritdoc
inner
instance
interface
kind
lends
license
listens
member
memberof
mixes
mixin
module
name
namespace
override
param
private
property
protected
public
readonly
requires
returns
see
since
static
summary
this
throws
todo
tutorial
type
typedef
variation
version
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | N/A |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {}
check-types
Reports invalid types.
Ensures that case of native types is the same as in this list:
boolean
number
string
Object
Array
Date
RegExp
Why not capital case everything?
Why are boolean
, number
and string
exempt from starting with a capital letter? Let's take string
as an example. In Javascript, everything is an object. The string Object has prototypes for string functions such as .toUpperCase()
.
Fortunately we don't have to write new String()
everywhere in our code. Javascript will automatically wrap string primitives into string Objects when we're applying a string function to a string primitive. This way the memory footprint is a tiny little bit smaller, and the GC has less work to do.
So in a sense, there two types of strings in Javascript; {string}
literals, also called primitives and {String}
Objects. We use the primitives because it's easier to write and uses less memory. {String}
and {string}
are technically both valid, but they are not the same.
new String('lard')
'lard'
new String('lard') === 'lard'
To make things more confusing, there are also object literals and object Objects. But object literals are still static Objects and object Objects are instantiated Objects. So an object primitive is still an object Object.
Basically, for primitives, we want to define the type as a primitive, because that's what we use in 99.9% of cases. For everything else, we use the type rather than the primitive. Otherwise it would all just be {object}
.
In short: It's not about consistency, rather about the 99.9% use case.
type name | typeof | check-types | testcase |
---|
Object | object | Object | ({}) instanceof Object -> true |
Array | object | Array | ([]) instanceof Array -> true |
Date | object | Date | (new Date()) instanceof Date -> true |
RegExp | object | RegExp | (new RegExp(/.+/)) instanceof RegExp -> true |
Boolean | boolean | boolean | (true) instanceof Boolean -> false |
Number | number | number | (41) instanceof Number -> false |
String | string | string | ("test") instanceof String -> false |
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | class , constant , enum , member , module , namespace , param , property , returns , throws , type , typedef |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
The following patterns are not considered problems:
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
newline-after-description
Enforces a consistent padding of the block description.
This rule takes one argument. If it is "always"
then a problem is raised when there is a newline after the description. If it is "never"
then a problem is raised when there is no newline after the description. The default value is "always"
.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | N/A |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
no-undefined-types
Checks that types in jsdoc comments are defined. This can be used to check unimported types.
When enabling this rule, types in jsdoc comments will resolve as used variables, i.e. will not be marked as unused by no-unused-vars
.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param , returns |
The following patterns are considered problems:
function quux(foo) {
}
The following patterns are not considered problems:
function quux(foo) {
}
class MyClass {}
function quux(foo) {
console.log(foo);
}
quux(0);
const MyType = require('my-library').MyType;
function quux(foo) {
}
import {MyType} from 'my-library';
function quux(foo, bar, baz) {
}
function quux(foo, bar) {
}
function quux(foo) {
}
function quux(foo) {
}
require-description-complete-sentence
Requires that block description and tag description are written in complete sentences, i.e.,
- Description must start with an uppercase alphabetical character.
- Paragraphs must start with an uppercase alphabetical character.
- Sentences must end with a period.
- Every line in a paragraph (except the first) which starts with an uppercase character must be preceded by a line ending with a period.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param , returns |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function longDescription (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
require-description
Requires that all functions have a description.
- All functions must have a
@description
tag. - Every description tag must have a non-empty description that explains the purpose of the method.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | class , example |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
require-example
Requires that all functions have examples.
- All functions must have one or more
@example
tags. - Every example tag must have a non-empty description that explains the method's usage.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | example |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
require-hyphen-before-param-description
Requires a hyphen before the @param
description.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
require-param-description
Requires that @param
tag has description
value.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
require-param-name
Requires that all function parameters have name.
The @param
tag requires you to specify the name of the parameter you are documenting. You can also include the parameter's type, enclosed in curly brackets, and a description of the parameter.
JSDoc
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
require-param-type
Requires that @param
tag has type
value.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
require-param
Requires that all function parameters are documented.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
require-returns-description
Requires that @returns
tag has description
value.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | returns |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
require-returns-type
Requires that @returns
tag has type
value.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | returns |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
require-returns
Requires returns are documented.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | returns |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
valid-types
Requires all types to be valid JSDoc or Closure compiler types without syntax errors.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param , returns |
The following patterns are considered problems:
function quux() {
}
The following patterns are not considered problems:
function quux() {
}
function quux() {
}
function quux() {
}