JSDoc `@private` on constructor without parameters is omitted in declaration files

🔎 Search Terms

jsdoc private constructor

🕗 Version & Regression Information

• This is the behavior in every version I tried back through TS 3.8 where JSDoc support was added, and I reviewed the FAQ for entries about JSDoc

⏯ Playground Link

https://www.typescriptlang.org/play/?target=99&module=1&ts=5.5.0-beta&ssl=8&ssc=10&pln=1&pc=1&filetype=js#code/MYGwhgzhAEBiD29oG8BQ0PQPQCofs2h2gAEAHAJwEsA3MAFwFMDMcsXph4A7CeigK7B68CgAoAlCgC+qWam6MA7nESSgA

💻 Code

// foo.js
class Foo {
    /**
     * @private
     */
    constructor() {}
}

new Foo()
// Constructor of class 'Foo' is private and only accessible within the class declaration.(2673)

🙁 Actual behavior

Emits the declaration file:

declare class Foo {
}

🙂 Expected behavior

Should emit the declaration file:

declare class Foo {
    /**
     * @private
     */
    private constructor();
}

Additional information about the issue

I ran into this as it was requested that TypeDoc add a new JSDoc tag to work around this issue. This seems wrong since the declaration file doesn't accurately describe the types within the file, but it's also very unfortunate that it results in the loss of any documentation added to the constructor.

https://github.com/TypeStrong/typedoc/issues/2577

Commencez par la reproduction liée dans TypeScript Playground en utilisant foo.js et comparez le fichier de déclaration généré avec la sortie attendue. Suivez la manière dont le JSDoc @private du constructeur sans paramètre est représenté lors de la génération des déclarations. C'est terminé lorsque le .d.ts généré conserve le constructeur privé et sa documentation sans modifier le comportement d'accès au constructeur signalé.