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
Make basePath
configurable
#1924
Comments
The specific problem you're running into I believe will be resolved by 0.23, which adds a typedoc/src/test/converter/alias/specs.json Lines 22 to 29 in 03d948e
That said, I'm not opposed to a baseDir option which controls this, preventing the getCommonDirectory behavior. |
@Gerrit0 Will this |
Yes, url is included in the json in 0.23 |
Awesome, looking forward to it. |
Search terms
Monorepo, lerna, nrwl, fileName
Expected Behavior
Given a mono-repo with modules under a common directory, for example:
I'd expect
fileName
discovered forindex.ts
inmodule-A
(andmodule-B
) to include the common directory name, sopackages/module-A/src/index.ts
instead of justmodule-A/src/index.ts
Actual Behavior
To my understanding, when TypeDoc parses the sourcecode, it calls
getCommonDirectory
to automatically determine the root directory.However, for mono-repos that follow the structure recommended by Lerna (with all the public modules under
packages
), thefileName
determined by TypeDoc is incorrect since it misses the top-level sub-directory name.This then has a knock-on effect on other projects such as
docusaurus-plugin-typedoc-api
, which usefileName
to determine the location of the file in the GitHub repository - see milesj/docusaurus-plugin-typedoc-api#39Steps to reproduce the bug
See above
Proposed solution
It feels like making the
basePath
inonBeginResolve
configurable could solve this problem:Environment
0.22.13
4.6.3
16.13.1
The text was updated successfully, but these errors were encountered: