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
Right now the parent list item is not rendered in "Linked mentions", as you can see on the screenshots below. Is is possible to render these items? (I would expect it to have the same formatting as in the original page).
The text was updated successfully, but these errors were encountered:
This is certainly possible, but it might slow down the search and make it even more janky. Right now, most of the jank comes exactly from rendering markdown, imagine how performance would be impacted if we increased the amount of renders even further 😢
@ivan-lednev, understood, thanks for the explanation!
I've forked the project to try to implement this feature, since I've seen the "good first issue" label.
But in case you feel like this will impact performance a lot, feel free to close, since it's of course not an essential feature, only "nice to have" :)
@cakechaser, while feeding every breadcrumb to the markdown renderer is going to significantly slow things down, there are other things we could do:
Do what Obsidian does (e.g. inside its core 'Outline' plugin): strip away markdown tokens like ==, **. This is going to be very easy
mdast-util-to-string might be helpful
Replace the most common tokens with HTML tags manually (**bold** => <strong>bold</strong>). My guess is that it's not going to affect performance, while this kind of formatting is 90% of what you need from rendering breadcrumbs
Find a faster markdown compiler library and disable sanitizing
So I'll leave the issue open for now in case someone (maybe you 😅) will want to implement it.
Really awesome plugin, great work!
Right now the parent list item is not rendered in "Linked mentions", as you can see on the screenshots below. Is is possible to render these items? (I would expect it to have the same formatting as in the original page).
The text was updated successfully, but these errors were encountered: