-
-
Couldn't load subscription status.
- Fork 3.7k
Obsidian reader extensions for comments and wikilink transclusions #11135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Transclusion should be possible. See |
|
@jgm I think this is in a good place for your review now. Some notes:
|
479d5f1 to
7b2638d
Compare
|
Can you rebase this into one commit, or a few logically coherent commits? All API changes should be clearly described and marked as such |
626148c to
dbd8cdf
Compare
dbd8cdf to
ad204c0
Compare
Done! |
Add Obsidian-Flavored Markdown #9883 using Markdown extensions. I could use some guidance on the approach to transclusion, and what to do on the writer side.
Extensions
comments: Parses%%text%%as comments (removed from output)wikilink_transclusions: Parses![[Title]]for full file transclusionwikilink_heading_transclusions: Parses![[Title#Heading]]for heading transclusionswikilink_block_transclusions: Parses![[Title#^id]]for block transclusionsblock_ids: Parses^idat paragraph end, wraps paragraph inDivwith that IDUses
insertIncludedFilefor transclusion.Includes tests and manual updates.