-
Notifications
You must be signed in to change notification settings - Fork 708
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
excludeNotDocumented Won't Emit the Function Declaration #1994
Comments
Now this issue is Investigating by: @cary-hu |
Oops... how do I continuously forget about functions :/ This happens because functions don't have comments on their reflection, they instead have comments on their contained SignatureReflections https://github.com/TypeStrong/typedoc/blob/master/src/lib/converter/plugins/CommentPlugin.ts line 403ish |
Thanks for the reply. We are using d.ts. Hence, the functions are Declaration. When performing the fix, please don't forget about the .ts files. We should see if the comments inside methods and functions can be resolved correctly. What we see - just to remind - I've found the following behavior, and we saw a related-solved-PR: When If The Object type declaration have comment, but the fields inside type declaration DO NOT have comment, the fields will be exported (expected behavior). i.e.:
The fieldA still can be exported. This is by-design. Related PR: |
Explanation: Thanks. |
Copying from Discord for posterity:
|
Fixed by #1997 |
@Gerrit0 |
Search terms
excludeNotDocumented d.ts function Declaration
Expected Behavior
The function declarations should be generated when
excludeNotDocumented
istrue
in the following cases:Actual Behavior
The functions (call signatures) from above documents is not generated.
Steps to reproduce the bug
Step 1:
git clone https://github.com/capraynor/typedoc-method-declaration-not-extrated.git
Step 2:
run
npm run build-api-doc
Regarding to this file:
https://github.com/capraynor/typedoc-method-declaration-not-extrated/blob/master/packages2/module1/index.d.ts
case1 is not generated (not good)
case2 is not generated (OK, because it is private one AND
excludePrivate=true
)case3 is not generated (not good)
Please note that:
excludeNotDocumented = true
, the bug occurs.excludeNotDocumented=false
, everything works fine.Environment
0.23.7
4.7.4
v16.15.1
Windows
Will share more information if we've found a clue.
Feel free to comment if you know which point should we check.
The text was updated successfully, but these errors were encountered: