Skip to content
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

[BUG] Multilevel external documents tree is generated incorrectly #482

Closed
andriisalamatin opened this issue Feb 20, 2018 · 1 comment
Closed

Comments

@andriisalamatin
Copy link

andriisalamatin commented Feb 20, 2018

Overview of the issue

Multilevel external documents tree is generated incorrectly

Operating System, Node.js, npm, compodoc version(s)

MacOS 10.13.3, Node v7.10.1, npm 4.2.0, compodoc 1.0.7
...
"@compodoc/gulp-compodoc": "0.0.6",
...

Compodoc installed globally or locally ?

locally

Motivation for or Use Case

because it brakes pages documents tree

Reproduce the error

Use summary.json:

[
  {
    "title": "1",
    "file": "/1.md"
  },
  {
    "title": "2",
    "file": "/2/index.md",
    "children": [
      {
        "title": "21",
        "file": "/21/21.md"
      },
      {
        "title": "22",
        "file": "/22/22.md"
      },
      {
        "title": "23",
        "file": "/23/23.md"
      }
    ]
  },
  {
    "title": "3",
    "file": "/3.md"
  }
]

generate documentation

Expected navigation:

1
2
21
22
23
3

Results:

1
2
21
3
22
23

Suggest a Fix

Issue could not be reproduced in version 1.0.5, so as temporary fix can be direct specification old version:
...
"@compodoc/compodoc": "1.0.5",
...

This commit is probably source of issue
4061795

@andriisalamatin andriisalamatin changed the title [BUG] prepareExternalIncludes brakes multilevel pages documents tree [BUG] Multilevel external documents tree is generated incorrectly Feb 20, 2018
@vogloblinsky vogloblinsky added this to the 1.0.9 milestone Mar 3, 2018
@lock
Copy link

lock bot commented Sep 30, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants