-
-
Notifications
You must be signed in to change notification settings - Fork 738
Support for @ignore? #198
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
Comments
It would be very useful. I tried exclude files, but in my case typedoc can't generate doc because missing references. |
Did you try |
nope, will try that when I am back on the project. I find it odd though that in some areas it followed jsdoc and in others it just does its own thing. |
Yeah, I was lucky to find this feature in source code. |
Using |
it would also be nice if |
Typedoc doesn't currently support @ignore - it uses @hidden. (See TypeStrong/typedoc#198). Adding @hidden alongside the @ignore correctly supresses the fin.WindowOptions, which was generating invalid json (an array within an array for the child property), and correctly creates the WindowOptions documentation.
Typedoc doesn't currently support @ignore - it uses @hidden. (See TypeStrong/typedoc#198). Adding @hidden alongside the @ignore correctly supresses the fin.WindowOptions, which was generating invalid json (an array within an array for the child property), and correctly creates the WindowOptions documentation.
Typedoc doesn't currently support @ignore - it uses @hidden. (See TypeStrong/typedoc#198). Adding @hidden alongside the @ignore correctly supresses the fin.WindowOptions, which was generating invalid json (an array within an array for the child property), and correctly creates the WindowOptions documentation.
Reviewing this, I think it would be good to alias JSDoc's
|
I assume that the syntax typedoc uses is based off jsdoc, but I have noticed that it doesn't support all the common features, in this instance the
@ignore
option which should omit the related variable/class/property etc from the documentation.The text was updated successfully, but these errors were encountered: