You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some project use the old jsdoc or closure compiler style tags, so there are some tags jsduck cannot recognize and would output some warnings when generating docs.
Implementing a custom tag is a solution, but what we need is to just elliminate these warnings, not make sense of all these tags, a custome tag introduces ruby programming and extra .rb files
So it would be nice if we can specify some tags to be ignored in config file or command line arguments, such as:
jsduck --ignore-tags="@file, @overview, @inner"
The text was updated successfully, but these errors were encountered:
Disable all warning about unknown tags is a solution, but far from good. The warning is really useful to find out typos in doc comments, such as typing @param to @prarm or whatever, so it would still be nice if jsduck could disable warnings for specific tags by config.
The second improvement perfectly solve our problem:
Some project use the old jsdoc or closure compiler style tags, so there are some tags jsduck cannot recognize and would output some warnings when generating docs.
Implementing a custom tag is a solution, but what we need is to just elliminate these warnings, not make sense of all these tags, a custome tag introduces ruby programming and extra .rb files
So it would be nice if we can specify some tags to be ignored in config file or command line arguments, such as:
The text was updated successfully, but these errors were encountered: