-
Notifications
You must be signed in to change notification settings - Fork 709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: @since tag #2614
Comments
seeing same warning with |
With 0.26, TypeDoc now warns if a tag isn't recognized when being parsed:
This was added to make usage of tags which are effectively ignored by TypeDoc visible. TypeDoc will recognize block tags with context clues, so even something like: /**
* @nobodyKnowsWhyThisIsATag Some text
*/ will be parsed, probably "correctly" as intended by the author, despite not being recognized by TypeDoc. JSDoc defines 85 block tags, most of which have no effect on the documentation coming out of TypeDoc. For tags where there is no expected behavior beyond just rendering the tag, and are reasonably widely used, like For other tags like If you have tags in your comments which are not part of the default suite, you can tell TypeDoc about them with the blockTags option or through a tsdoc.json. |
@Gerrit0 Thanks! I thought I was going crazy. Thanks for adding this in to the main code base 👍 |
What is the syntax when providing
|
I don't recommend setting that option from the command line, as setting it overrides TypeDoc's default set of tags, so you'll have to provide every single tag you use... $ typedoc --blockTags @since --blockTags @param --blockTags @remarks |
Search Terms
Encountered an unknown block tag
So maybe I am wrong, but I had
@since
in my comments, and Typedoc format this correctly as "Since" with the version, yet now it's reporting that@since
is not a valid tag. Either it's a bug or, I guess, a new feature. I didn't know where to go in terms of the report... logged a feature request. I looked in the code and could not find anything.Problem
Suggested Solution
Add it as a valid tag since it seems to be outputting just fine:
The text was updated successfully, but these errors were encountered: