-
Notifications
You must be signed in to change notification settings - Fork 715
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
Constructor property parameters are not documented when --excludeNotDocumented is on #1261
Comments
This is not a suggestion, but a bug. Sorry for the wrong labelling. |
@samuraijack you might be interested in this |
Thanks for the report, I'll check soon |
Can not reproduce this one. I'm testing with this class definition: /**
* Has docs
*/
export class BaseClass {
/**
* Has docs
*/
some : number
// no docs
protected kind: number;
/**
* Has docs
*/
static instance: BaseClass;
// no docs
static instances: BaseClass[];
/**
* Has docs
* @param name
*/
constructor(readonly name: string){
}
} The constructor seems to be properly documented. Command line:
@judax Any additional info? |
@judax Perhaps you did not include the docs for the class itself? Then the whole class won't be included. |
Your test works but I still cannot make my code work: /** Represents a 2 float structure (i.e. a point in 2D). */
export class Float2 {
/**
* Constructs a 2 float structure instance.
*
* @param x The x component of the 2 float structure.
* @param y The y component of the 2 float structure.
*/
constructor(readonly x: number, readonly y: number) {}
} Here are my command line options:
|
Ok, thanks for the info! |
Seems to me related to #584. It also seems to me that there is no way to add Documentation to the auto-generated Properties (only the Parameters):
|
Search Terms
constructor parameter property documentation
Problem
When using
--excludeNotDocumented
, a class that declares properties in the constructor the properties do not seem to be documented correctly even with@param
.Suggested Solution
The text was updated successfully, but these errors were encountered: