-
Notifications
You must be signed in to change notification settings - Fork 685
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
typedoc does not respect tsconfig.json include and entryPoint should be supplied manually. #1515
Comments
Yes! It should. For the vast majority of cases, the
For many projects, {
"out": "../_site/api",
"json": "../_site/api/docs.json",
"name": "TypeDoc Documentation",
"excludeExternals": true,
"includeVersion": true,
"entryPoints": ["src/index.ts"]
} There has been some discussion in #1485 about automatically detecting the entry point using the |
Thanks for your quick response!
|
Oh! That makes sense why you thought what you did then. I must have forgotten to update that part of the page when 0.20 was released. That was accurate for older versions of TypeDoc... I'll update that shortly. |
Thanks! |
.. and consequently, the type therein `InvokeOptions`, in generated docs. All functions in Pulumi SDKs take an InvokeOptions-typed argument, and all the generated documentation for those functions has a broken link because it's not part of the NodeJS SDK documentation generated for pulumi/pulumi. The version of TypeDoc used is quite old, and I suspect it consults `tsconfig.json` to find the source files (evidence: someone complaining that it does not do this well enough: TypeStrong/typedoc#1515). I have conservatively just added the file in question to `files`, since: - I'm not sure if .files should list _all_ the files - Upgrading TypeDoc would surely have many unintended consequences Signed-off-by: Michael Bridgen <mbridgen@pulumi.com>
…tation (#9973) * Make tsconfig.json valid JSON * Include invoke.ts in tsconfig.files .. and consequently, the type therein `InvokeOptions`, in generated docs. All functions in Pulumi SDKs take an InvokeOptions-typed argument, and all the generated documentation for those functions has a broken link because it's not part of the NodeJS SDK documentation generated for pulumi/pulumi. The version of TypeDoc used is quite old, and I suspect it consults `tsconfig.json` to find the source files (evidence: someone complaining that it does not do this well enough: TypeStrong/typedoc#1515). I have conservatively just added the file in question to `files`, since: - I'm not sure if .files should list _all_ the files - Upgrading TypeDoc would surely have many unintended consequences
Search terms
typedoc, tsconfig, include, exclude
Expected Behavior
I have the following
tsconfig.json
file:I expect that when I enter the following command in terminal, the output be generated, but It doesn't work.
$ typedoc
But when I change it to this, it works as expcted:
$typedoc src
Actual Behavior
The following output is shown:
Steps to reproduce the bug
Environment
The text was updated successfully, but these errors were encountered: