-
-
Notifications
You must be signed in to change notification settings - Fork 738
The @internal doc flag recognised by tsc should be an alias for @hidden #364
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
Great idea! Looks like these lines are where the Should the |
Should consider adding |
I wrote a plugin for my project which allows me to mark specific code as https://github.com/christopherthielen/typedoc-plugin-internal-external The plugin also allows you to specify aliases for each annotation. https://github.com/christopherthielen/typedoc-plugin-internal-external#annotation-aliases |
@christopherthielen I noticed your plugin just this week. The aliases look like a great opt-in way to workaround this so thanks for sharing. I think it would be great to have some documentation pointing people to 3rd party plugins like this. I've been hesitant to merge #525 because Actions steps I think should be taken
|
Does |
TypeDoc doesn't produce declaration files, so I don't think it's a TypeDoc issue. The TypeScript compiler options page doesn't list all options, nor does |
The
@internal
flag is used bytsc --stripInternal
to exclude a particular property from a generated declaration file. If you're producing a documented library with public methods for consumption this is basically the same as the@hidden
flag you'll want to use in your typedoc.It would be great if I could just use
@internal
and have it work on both my.d.ts
and typedoc output.I realise PRs are needed to make progress on typedoc at the moment but I thought I'd put this up as an issue in case anybody has any better ideas!
The text was updated successfully, but these errors were encountered: