[BUG] Markdown hierarchy appearing wrong in navigation panel about qownnotes HOT 8 CLOSED

Hm, the used "algorithm" searches for the previews heading that is one level higher, that is ### 1.1.3 in your example, since you skipped the proper ### heading after ## 2.2.

from qownnotes.

Hm, the used "algorithm" searches for the previews heading that is one level higher, that is ### 1.1.3 in your example, since you skipped the proper ### heading after ## 2.2.

Yeah, I skipped h3...

Like I said, maybe I use the hierarchy in a 'particular' way, but I thought the algorithm should also consider the typing position in the file.

To explain better, I always start typing subjects using h4 and under it I put

(normal text) to explain in details, if the issue belongs to some group, I add h3, h2 and h1 to organize it, for better understanding and visualization of priorities.

If what I did is considered wrong, I apologize and ask you to close the issue

Sorry for my English

from qownnotes.

If what I did is considered wrong, I apologize and ask you to close the issue

"Wrong" is a harsh word. 😊 It's more like in HTML or Markdown you are not supposed to skip heading level...

The current implementation of finding a suitable parent is:

Works great for a valid Markdown heading structure. ️🤷🏻

from qownnotes.

If what I did is considered wrong, I apologize and ask you to close the issue

"Wrong" is a harsh word. 😊 It's more like in HTML or Markdown you are not supposed to skip heading level...

The current implementation of finding a suitable parent is:

Works great for a valid Markdown heading structure. ️🤷🏻

Yeah, like you said, it's not recommended.

I took a quick read at this interesting discussion about this topic:
Heading off confusion
The entire text is interesting, but the comments are gold... No consensus at all if skipping headings should be considered wrong (prohibited) or just 'non-recommended' but acceptable.

Initially, when i opened the ticket I just wanted to show this 'unexpected' behavior to the devs; well, it's done.
If you consider the behavior normal, well, I'll adapt and live with this.

You've been very kind regarding this issue, thank you!

And again, sorry for my broken English

from qownnotes.

You've been very polite too! 🙏🏻
I'm not even sure on how easy it would be to do anything about it and if it would cause problems in different cases...

from qownnotes.

Phew, it's rather hard to find a more suitable parent item if the structure isn't valid...

from qownnotes.

This issue is stale because it has been open for 30 days with no activity.

from qownnotes.

This issue was closed because it has been inactive for 14 days since being marked as stale.

from qownnotes.