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
@param names are not rendered #1410
Comments
This is due to the template partial for comment tags - it you to use |
This is the output of the same from https://microsoft.github.io/tsdoc As you can see, it works correctly. |
TSDoc != TypeDoc. TypeDoc doesn't currently conform to the TSDoc standard, though support for it is planned. That demo is particularly misleading because it doesn't parse the source code - it only grabs a comment and then renders it. I suspect that if you ran that code through api-extractor, it would complain about your use of |
This defect also applies to the TypeScript binding syntax for member functions: class MyClass {
/**
* Function that does stuff
*
* @param param1 - The first param
* @param param2 - The second param
*/
protected boundFunction = (param1: string, param2: number): void {} Is there another way to document this syntax? |
I encounter what I think is the same problem in the context of a function type definition. /**
* @param a The first number
* @param b The second number
*/
export type MyFun = (a: number, b: number) => void; ...gets rendered like... Note the elements inlined in the comment which are marked I am invoking the build command with no arguments...
|
That's a different bug - #799. |
Thanks for your attention @Gerrit0 I've subscribed to that one. |
Search terms
@param hyphen
Expected Behavior
The name of the param should be visible next to the 'param' field. The @param block is followed by a parameter name and then a hyphen.
Actual Behavior
The generated document omits the actual param names and just lists the description.
Steps to reproduce the bug
Environment
The text was updated successfully, but these errors were encountered: