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
Obsidian Export behaves like Obsidian, that is, it exports 2.md with the following content:
Some highlights
Actual result
Obsidian export transcludes the whole 1.md file:
Some text
Some highlights ^some-block-id
Workaround
Use headings instead of block ids, which Obsidian Export does export correctly. However hopefully this is easy to fix given that Obsidian Export already supports headings?
The text was updated successfully, but these errors were encountered:
I am also interested in implementing this feature,but I am new to Rust. My idea is the implementation is not straight forward.
One way to implement would require to modify inherent parser used by obsidian export. We need to modify the definition of block. A block may have an id, since block is not provided tags
block_element -> block_element id
id -> "" | id -> ^number
Maybe it can be implemented as post processor, for each block event we can extract the ^block id using regex and store it and later use them while embedding.
I would love to hear if there could be simple approach without modifying the library and just use post processor to do it.
How to reproduce
Create two notes:
1.md:
2.md:
Expected result
Obsidian Export behaves like Obsidian, that is, it exports 2.md with the following content:
Actual result
Obsidian export transcludes the whole 1.md file:
Workaround
Use headings instead of block ids, which Obsidian Export does export correctly. However hopefully this is easy to fix given that Obsidian Export already supports headings?
The text was updated successfully, but these errors were encountered: