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
Transclusions/Note embeddings cause hydration errors #545
Labels
Comments
@Mr-Pine thank you for submitting the issue! I totally agree, Obsidian note embeds shouldn't throw an error and at least temporarily should be converted to links. I'll take care of it! |
olayway
changed the title
Transclusions/Note embedding
Transclusions/Note embeddings cause hydration errors
Aug 10, 2023
2 tasks
olayway
added a commit
that referenced
this issue
Aug 14, 2023
olayway
added a commit
that referenced
this issue
Aug 14, 2023
@Mr-Pine This has just been fixed. Thanks again for reporting this issue! 🌷 |
Awesome! |
rufuspollock
pushed a commit
to rufuspollock/flowershow
that referenced
this issue
Oct 27, 2023
olayway
added a commit
that referenced
this issue
Oct 31, 2023
olayway
added a commit
that referenced
this issue
Oct 31, 2023
olayway
added a commit
that referenced
this issue
Oct 31, 2023
olayway
added a commit
that referenced
this issue
Oct 31, 2023
olayway
added a commit
that referenced
this issue
Oct 31, 2023
nyejon
pushed a commit
to nyejon/flowershow_blog
that referenced
this issue
Nov 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently, if a markdown file contains an Obsidian-style transclusion like
![[my-other-note.md]]
you get an error in dev modeError message
and nothing happens in export mode.
I understand that that is a pretty big feature, but I have found very litte (up to date) information on whether and when support for transclusions is planned.
In the meantime, it might make sense to transform transclusions into normal links, so that not all functionality is lost and the site is not unusable in dev mode
The text was updated successfully, but these errors were encountered: