RFC: Core set of tags for TSDoc
See original GitHub issueTSDoc should define a core set of tags for very common scenarios, so their semantics can be standardized across all tools.
Ignoring the syntax details for a moment, which tags should be included in this list?
Here’s some suggestions from AEDoc:
@param
@returns
{@link
}{@inheritdoc}
@remarks
Any others?
Issue Analytics
- State:
- Created 5 years ago
- Comments:29 (6 by maintainers)
Top Results From Across the Web
Project roadmap - TSDoc
That said, here's some feature areas seen as the main priorities for future investments: Collect all the design specifications from the GitHub “RFC”...
Read more >@microsoft/tsdoc | Yarn - Package Manager
Rename CoreTags to StandardTags so we can include non-core tags in the standard definitions · Rename CoreModifierTagSet to StandardModifierTagSet and convert ...
Read more >@microsoft/tsdoc@0.14.2 - jsDocs.io
Documentation for npm package @microsoft/tsdoc@0.14.2 - jsDocs.io. ... Returns the full list of all core tags. ... RFC 1738 for syntax.
Read more >tsdoc.json - API Extractor
It can be extended with custom tag definitions. API Extractor's custom tags are referred to as “AEDoc” tags. They are defined in the...
Read more >TSDoc(完成) - 噬蛇之牙- 博客园
By itself, the @microsoft/tsdoc package is not a documentation ... TSDoc tags in the “Core” standardization group are considered essential.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems reasonable. However strict mode should enforce that
@see
always appears at the start of a line, and always after the main content. Before we eliminated it, we found a lot of people writing this kind of thing:Please consider:
async
public
private