-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Ambiguous docs on local inventories #9
Comments
No, that cannot work: this would not provide any information about the project root URL (what the URLs in the inventory are relative to). You have to use
I'll make sure to clarify this. Thanks for pointing out the broken link! |
@tecosaur Have a look at http://juliadocs.org/DocumenterInterLinks.jl/dev/api/internals/#DocumenterInterLinks.InterLinks Does that updated documentation seem sufficient to make it non-ambiguous? |
Thanks! That does indeed help, particularly the explanation about how the Julia example works. I've yet to actually try an InterLinks(
"DataToolkitCore" => (
"https://tecosaur.github.io/DataToolkit.jl/core/",
joinpath(dirname(dirname(@__DIR__)), "Core", "docs", "build", "objects.inv")
),
"DataToolkitREPL" => (
"https://tecosaur.github.io/DataToolkit.jl/repl/",
joinpath(dirname(dirname(@__DIR__)), "REPL", "docs", "build", "objects.inv")
),
"DataToolkitStore" => (
"https://tecosaur.github.io/DataToolkit.jl/store/",
joinpath(dirname(dirname(@__DIR__)), "Store", "docs", "build", "objects.inv")
),
"DataToolkitCommon" => (
"https://tecosaur.github.io/DataToolkit.jl/common/",
joinpath(dirname(dirname(@__DIR__)), "Common", "docs", "build", "objects.inv")
),
"DataToolkitBase" => (
"https://tecosaur.github.io/DataToolkit.jl/base/",
joinpath(dirname(dirname(@__DIR__)), "Base", "docs", "build", "objects.inv")
),
"DataToolkit" => (
"https://tecosaur.github.io/DataToolkit.jl/main/",
joinpath(dirname(dirname(@__DIR__)), "Main", "docs", "build", "objects.inv")
),
) 🙂 |
Great! That looks like it should work! |
Hello!
Looking at the
InterLinks
docstring (the link in the second paragraph of the readme is broken BTW), it's not clear ifwould work or not. If you could clarify this, that would be great 🙂
This is something I'm interested in since I'm currently restructuring a sextet of related packages of mine into a mono-repo, with each package (and their
docs
subfolder + inventory) in a subfolder of the main repo.The text was updated successfully, but these errors were encountered: