TocGenerator doesn't link to generated index.md the first run, and contains index while parent item links to it

[CodeCasterNL]

Given this directory structure:

• A
  • B.md
• index.md

Running DocFxTocGenerator.exe --docfolder DocFxIndex --index, the toc.yml contains:

items:
- name: DocFxIndex
  href: index.md
- name: A
  href: A/B.md # links to B.md instead of index.md
  items:
  - name: A
    href: A/index.md # generated
  - name: B
    href: A/B.md

Issue 1:

The root-level item "A" links to A/B.md, because at generation-time the A/index.md didn't exist yet.

Running the TOC generator a second time fixes that:

items:
- name: DocFxIndex
  href: index.md
- name: A
  href: A/index.md # now links to A/index.md
  items:
  - name: A
    href: A/index.md # there's A/index.md again!
  - name: B
    href: A/B.md

Issue 2:

Now the TOC contains "A/index.md" twice, resulting in weird nesting in the menu, mentioning "A" twice:

Expectations

I would expect:

• The index.md generation to be done depth-first, so the index.md can be added as the directory link instead of the next first file found (in other words, that the TOC generation with --index is stable).
• An item with children that links to an index.md not to contain the index.md as item again.

So:

items:
- name: DocFxIndex
  href: index.md
- name: A
  href: A/index.md # immediately links to the generated index
  items:
  # doesn't mention it again as child item
  - name: B
    href: A/B.md

[mtirionMSFT]

@CodeCasterNL After another investigation of this problem I found that your scenario still results in the wrong output where the index.md is ignored. I have fixed it in #57 and it will be released soon. Sorry for the delay.