JSDoc
Documentation-comment validation rules. Bundles eslint-plugin-jsdoc content checks (tag names, parameter coverage, descriptions) with the lone eslint-plugin-tsdoc syntax check (jsdoc/tsdoc-syntax). Both target /** ... */ comments. Formatting concerns (alignment, indentation) are configured through the top-level format block, not here.
Source: eslint-plugin-jsdoc (BSD-3-Clause, attribution required), eslint-plugin-tsdoc (MIT).
jsdoc/check-tag-names: Reject unknown JSDoc block-tag names.jsdoc/check-values: Validate@accessvalues against the closed setpublic,protected,private,package.jsdoc/empty-tags: Reject content on marker-only JSDoc tags (@async,@public,@override, β¦), these tags take no value.jsdoc/no-types: Reject JSDoc type braces in TypeScript sources, since the surrounding TypeScript already carries the type.jsdoc/reject-any-type: Rejectanyand*inside JSDoc type braces. These escape the documented type system the same way TypeScriptanydoes.jsdoc/reject-function-type: Reject the unsafeFunctiontype inside JSDoc type braces.jsdoc/require-description: Require JSDoc blocks to include a leading block-level description. Every documented identifier should explain itself.jsdoc/require-param-description: Require every@paramtag that names a parameter to also carry a description after the name.jsdoc/require-param-name: Require every@paramtag to include the parameter name it documents.jsdoc/require-property-description: Require every@propertytag that names a property to also carry a description.jsdoc/require-property-name: Require every@propertytag to include the property name it documents.jsdoc/require-returns-description: Require every@returnstag to carry a description of the returned value.jsdoc/tsdoc-syntax: Detect structural TSDoc problems in documentation comments: malformed top-level block tags (@followed by non-letter) and malformed or unclosed inline tags ({@link ...}).
Last updated on