Hi guys,
I haven't seen a way to exclude dependencies when building docs. Ideally I only want to produce documentation for my own package.
I'm currently building docs with:
dub build -b docs
I imagine that I might need to specify a configuration in my dub.json?
Thanks,
On Mon, 19 Dec 2016 03:07:44 GMT, Joshua Hodkinson wrote:
Hi guys,
I haven't seen a way to exclude dependencies when building docs. Ideally I only want to produce documentation for my own package.
I'm currently building docs with:
dub build -b docsI imagine that I might need to specify a configuration in my dub.json?
Thanks,
That should in fact only build documentation for the current package. To include everything, using --combined should be required (both is also what happens in practice for me).
If building with -b ddox, individual package namespaces can also be excluded by adding x:ddoxFilterArgs "--ex" "some.package." (or "-ddoxFilterArgs": ["--ex", "some.package."] for dub.json).
On Mon, 19 Dec 2016 11:59:46 GMT, Sönke Ludwig wrote:
On Mon, 19 Dec 2016 03:07:44 GMT, Joshua Hodkinson wrote:
Hi guys,
I haven't seen a way to exclude dependencies when building docs. Ideally I only want to produce documentation for my own package.
I'm currently building docs with:
dub build -b docsI imagine that I might need to specify a configuration in my dub.json?
Thanks,
That should in fact only build documentation for the current package. To include everything, using
--combinedshould be required (both is also what happens in practice for me).If building with
-b ddox, individual package namespaces can also be excluded by addingx:ddoxFilterArgs "--ex" "some.package."(or"-ddoxFilterArgs": ["--ex", "some.package."]for dub.json).
Is that still applicable in a vibe app?
