- Bear Version: 2.4.3
- OS Version: Mac OS 15.5, and iOS 18.4.1
- What were you doing: folding/collapsing lists that included headers
- What feature did you use: folding
- What happened: If a list item is also a header it cannot be folded/collapsed
- What did you expect to happen: all headers and list items would be foldable/collapsable
This is by design, and the reason is a bit technical. The use case is rather small and it adds an unproportional amount of complexity to the code.
thanks for clarifying
Thanks for clarifying but I don’t agree with this design choice and would like to second bpeps563 issue report. From a users perspective it’s not understandable why the behaviour is different in various cases. In my particular instance it makes the folding feature unusable since I often combine bullet points and headings.
We tried to allow it but it made the feature much more complicated to implement. In the end it is about priorities.
I have to agree with the devs on this design. I’ve never seen a heading inside a hierarchy of bullets or adding a bullet to a heading over the years of using various Markdown apps. This would be the first for me. I see headings as the top and everything underneath gets random emphasis.
In this case, bold, underline (which is rare), and the new and excellent highlight colors (also rare) would be good to make the emphasis stand out on a bullet. You could also get creative with the new callouts feature.
If TOC and folding is needed, the best practice I would follow is remove the bullet and make it the next heading in the hierarchy (H2 to H3). I think you’ll find this more common when bouncing to other Markdown apps.
1 Like
@AdamRadPro Thank you for your input and ideas for possible workarounds. I myself like to structure my notes in a similar fashion to roam research, where I have the possibility to use indentation coupled with sectional hierarchies. This allows for tremendous flexibility in my note taking and greatly improves structurability and therefore readability and scanability of (especially) longer notes. There are many, many examples of similarly structured notes online. See two examples from different online authors of the feature I’m proposing:
BTW: Obsidian handles the combination of bullet points and headers as expected and I’m sure that’s no coincidence as the explanation of rexikan seems to suggest. And also Bear allows the combination of these elements, it’s just the folding mechanism that “breaks”.
@rexikan Thanks for your clarification. Being an app developer myself I can relate to the importance of prioritisation. The feature request on my part still stands. For the time being I guess I will just not use any folding in my notes 
I would argue from a traditional point of view. The purpose of headings is to structure a text. In this sense, it makes no sense to allow headings within a list at all. I don’t even want to talk about absurd results such as using a higher heading for each deeper level within a list. A heading is a heading and nothing else. I find it confusing that it is even possible to use a heading within a list.
On the other hand, however, I find the existing option of using headings within quotations/callouts, for example, at least not absurd, even if I don’t really see the benefit. But then I would at least expect these headings not to be included in the TOC, because they suggest a structure of the text that does not actually exist. These headings do not structure the entire text, but only the text within the callouts. It’s like a matryoshka doll.