You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having something like this (having items with level above 1 after empty level) breaks navigation parsing with 500 error.
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?
The text was updated successfully, but these errors were encountered:
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.)
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.
Having something like this (having items with level above 1 after empty level) breaks navigation parsing with 500 error.
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?
The text was updated successfully, but these errors were encountered: