Already it's very useful! And thanks for your goodwill in sharing!
A killer feature for me in the latest version was the ability to collapse headers in rendered view. That's a feature I never found elsewhere. I went back to the stable version, as code rendering in the blocks was mis-rendering as markdown.
Still daily using your Copy-Span and Collapsible-Blocks, very nice additions to Joplin!
Could you give an example of what was causing this bug? I wasnāt able to reproduce it just now, but it sounds similar to a bug I remember encountering a few months ago, that I forgot to write down and then forgot how to reproduce I may not be the most organized.
I do have plans to make the headers (have the option to) remember whether they were opened/closed, as was requested by someone in another thread. I havenāt started on that yet though, and Iām expecting the solution I have in mind to only work on desktop, not mobile, which I donāt like but itās better than nothing. Iād also like to make the headers collapsible in the editor. Honestly I canāt say Iām super pleased with the current state of the plugin, and Iāve considered just starting it over from scratch - but that seems like a good way to make sure the next release just never happens at all.
I meant in your dev version in the webview the little arrow added to right of headers, giving the ability to collapse header content by clicking on the headersāthat was an excellent aid in navigation long notes in the reading view!
The bug seems to be caused by any header appearing before a code block with content bounded by your fences. Here is a note to demonstrate:
@johano Thanks for the test note Iām on the wrong machine to test this right now but it should be super useful later on. Iām thinking I might release the next version as a bugfixed version of the dev version you tried so something is out, then see if I can get through some major rewrites after that. Maybe I should finish up letting headers collapse in the editor and remember their state, as well.
@executed Thatās not quite what I meant about issues with mobile - I use Android and donāt have an iOS device. But the solution I had in mind for remembering if headings were left open or not, without adding any extra data to notes, was to save an external file that stored that information. I remembered earlier in this pluginās development that the API offers some functionality like that, and I very briefly tested it out, before finding it didnāt work on mobile, at which point I moved on to other things.
But⦠Rereading the API now, I donāt think I noticed the joplin.data.getUserData options before, and they seem perfectly up to the task - Iāll have to test out if that works on mobile.