-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Documentation tool is missing #15520
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
Check out |
I'd have to +1 this and explicitly insist that (An alternative might be shipping a tsdoc.exe deliverable, but that would be exactly that, a separate deliverable.) Additionally, (if I understand having TS' compiler targets correctly) having that functionality in tsc would make it easier for to use it on "non-.exe" targets and platforms. |
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed. |
@mhegazy This issue is not a question and it is not unactionable. |
#10 is tracking that. |
I usually use Doxygen to generate documentation for my PHP and C++ projects. I would like to use it for TypeScript code as well. I looked for tools to build the docs and found nothing, except a feature request in JSDoc — jsdoc/jsdoc#272.
The documentation generator should scan source code tree and produce HTML output with the desired documentation, or provide a dox file for Doxygen. The dox file would be better as Doxygen already knows how to deal with the HTML output. Or it could integrate to any other widely-used documentation generator. The tool must be independent of any IDE, so it can be used in automated CI builds.
In case the documentation tool already exists, there should be a page in the TS documentation dedicated to it, so developers know what to use.
In case the documentation tool does not exist, it would be nice to add dox output to
tsc
so thetsc --dox
can be used as input filter for Doxygen. It should be quite simple to implement as it only needs to collect doc comments and prepend them with few doxygen commands (very similar to javadoc) to specify class/method/function name, parameters, and types. It could be done the same way astsc --declaratinon
.The text was updated successfully, but these errors were encountered: