URL with subtree

[melissawm]

Context

I am trying to build a website stitching two documentation sets together - one local to my repo, an another external to another repo, served on the web.

Proposal

For this, it would be great to have a _toc.yml file setting up the navigation with a section that would be made up of URLs organized in subtrees. I know this is currently not possible (I get a [etoc] entry contains incompatible keys 'url' and 'subtrees' @ '/subtrees/0/entries/1'error) but my question is whether this is something that could be done? I'm happy to try and submit a PR if the general idea is reasonable.

Tasks and updates

No response

[n8willis]

Although I don't have any information that would help lead towards a solution (or a workaround), it sounds to me like this is the same underlying issue as #89 (which was opened by myself); the parser checks each item/node/thing in the tree here an complains if it sees anything that is not one of FILE_KEY, GLOB_KEY, URL_KEY ... presumably because those are the node types that will get a hyperlink of some kind or other.

The problem is that it's doing that check starting with the subtree node/element/item, rather than recognizing that it has encountered a subtree and thus needs to descend one more level deep.

I don't know why (like, if there is perhaps some valid reason) it's doing that. To me, it looks like it's clear-cut as as erroneous check. But unfortunately it just doesn't look like the team has any interest. I saw no response on my issue either.

But I do think you're correct and, from what I have gleaned, it sounds more than reasonable — if you were still considering developing a PR.