feat: structuredTags
setting to control type/name portions of existing or custom tags
#610
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(
check-types
,no-undefined-types
,valid-types
): AddstructuredTags
setting to control whether the type and namepath portions should be checked for validity and whether such portions are required, and to let user-defined "namepath-defining" tags be added to defined types. Closes #481BREAKING CHANGE:
Drops
checkSeesForNamepaths
setting. Use{settings: {jsdoc: {structuredTags: {name: 'namepath', type: false, required: ['name'],}}}}
instead.Also:
typdef
now requiresallowEmptyNamepaths: false,
to report empty names (as with other tags)event
andexternal
(andextends
in jsdoc mode); some tweaking of other tags per docs(Also does some jsdocUtil refactoring along the way to pull tag meta-data all into one map for easier management and to minimize tag-specific handling blocks within
valid-types
.)(Since settings can now throw, needed to add a test to a few other rules to cover such cases.)