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
#547 mentions that a goal of future TypeDoc versions is to be compliant with TSDoc.
@deprecated is a core TSDoc standard that is used by many tools, including IDEs like VSCode to indicate deprecation.
Although @alpha and @beta are "discretionary" modifiers, they are used by API Extractor and many Microsoft APIs (e.g. rush, heft, etc), and I believe are quite useful.
I propose we either add a strikethough, "gray out" the name, or add an icon next to items that are marked deprecated.
I also propose we add icons/tags in the UI next to items that are marked @alpha and @beta.
These are likely less important than other core TSDoc features like @linking, etc, so it may likely be implemented later.
Thanks for an awesome tool!
The text was updated successfully, but these errors were encountered:
Here is a commit you could reference where we support @obsolete (before deprecated was a thing), maybe for Hacktoberfest I could add this for @deprecated
#547 mentions that a goal of future TypeDoc versions is to be compliant with TSDoc.
@deprecated
is a core TSDoc standard that is used by many tools, including IDEs like VSCode to indicate deprecation.Although
@alpha
and@beta
are "discretionary" modifiers, they are used by API Extractor and many Microsoft APIs (e.g. rush, heft, etc), and I believe are quite useful.I propose we either add a strikethough, "gray out" the name, or add an icon next to items that are marked deprecated.
I also propose we add icons/tags in the UI next to items that are marked
@alpha
and@beta
.These are likely less important than other core TSDoc features like
@link
ing, etc, so it may likely be implemented later.Thanks for an awesome tool!
The text was updated successfully, but these errors were encountered: