-
Notifications
You must be signed in to change notification settings - Fork 710
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
projectDocuments in a merge
entryPointStrategy site
#2801
Comments
Yes, this is supported! I just pushed a gh2801 branch to typedoc-packages-example which demonstrates it (build with the advanced settings in the readme to replicate your JSON setup) Note that the documents for sub-projects will show up within the module created for that project, not at the top level. |
I see, thanks for the example. My problem was that I had his at the root typedoc (the one merging). and it was removing the projectDocuments. Dont know if this would count as a bug.
repro here https://github.com/alexprudhomme/typedoc-merge-documents |
That repo has an old version of typedoc installed - before 0.27 categorization/grouping wasn't performed on merged projects, so yes, it won't work there. |
Hi, I updated to the latest version and it still does not work. I have tried many setups and could not find one where I had categories/group + sub package documents. I updated the repo if you want to take a look. https://github.com/alexprudhomme/typedoc-merge-documents |
That's a bug! The group/category restoration code missed checking for documents, easy fix at least. |
Thanks a lot ! I suppose this will be in 0.27.5 ? |
Yes, likely this weekend, there are a couple other issues I want to look at |
Search terms
entryPointStrategy, merge, projectDocuments, documents
Question
Hi,
I am having trouble setting up projectDocuments for my typedoc site.
I am building a Typedoc site with
"entryPointStrategy": "merge"
, that takes in two --json builded sites. Project documents work fine in the root Typedoc project. However if I try to add some in the two --json builded site, they don't show up.They seem to show up as "documents" in the json file so I am not sure what I am doing wrong. Before digging up further, is this something that is supported ?
The text was updated successfully, but these errors were encountered: