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

500 error when navigation table has rows without level #134

Open
bartaz opened this issue Jun 21, 2022 · 1 comment
Open

500 error when navigation table has rows without level #134

bartaz opened this issue Jun 21, 2022 · 1 comment

Comments

@bartaz
Copy link
Contributor

bartaz commented Jun 21, 2022

Not sure if it's a bug or "feature", but seems that having navigation table items without level between items that have level breaks the nav parsing.

[details=Navigation]
| Level | Path | Navlink |
| -- | -- | -- |
| 1 | test1 | [Heading1](https://discourse.ubuntu.com/t/how-to-write-and-format-discourse-specs/27036) |
| 1 | test2 | [Heading2](https://discourse.ubuntu.com/t/segmented-control-component/26835) |
| | test-hidden | Test |
| 2 | test3 | [Heading2](https://discourse.ubuntu.com/t/segmented-control-component/26835) |
| 3 | test4 | [Heading2](https://discourse.ubuntu.com/t/segmented-control-component/26835) |
| 3 | test5 | [Heading2](https://discourse.ubuntu.com/t/segmented-control-component/26835) |
[/details]

Having something like this (having items with level above 1 after empty level) breaks navigation parsing with 500 error.

Screenshot 2022-06-21 at 15 00 07

I don't know if rows without level have any special meaning, but maybe they should just be ignored, and not make the navigation parsing break?
Or is this expected to have level 0 or 1 after empty level for some reason?

@tmihoc
Copy link
Member

tmihoc commented Jun 22, 2022

Hi. It would really help to have either support for level 4 or for level null (leaving the level empty). I have a lot of level 4 or even 5 entries in my docs, and I understand if we cannot display them in the Navigation bar for space reason, but it would help me to see them there in the Navigation table so I know to reference them from the parent level doc. (Available for a call if that helps.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants