This release is about keeping your notes exactly as you wrote them. Wiki embeds like ![[image.png]], email autolinks, and links with spaces in the path now stay intact when documents are normalized or rewritten. inline no longer copies the inlined note's frontmatter into the host. $section updates hit the section once, and --strict --dry-run previews now report schema violations the same way a real run does.
Thanks to @robfeldmann for reporting these issues (#428, #429, #430, #431, #432).
iwe
Fixed
- Wiki embeds (
![[image.png]],![[image.png|300]]) are kept as written when a document is re-rendered bynormalize,renameand other commands (previously rewritten as Markdown images) - Link and image destinations containing spaces are written as
<path with spaces>so they stay valid Markdown update --delete,--insert-afterand other block operators treat a$sectionas one target, soexpect: 1passes and inserted content lands once below the section (previously applied to every block in the section when it was not the first block under its parent)- Email autolinks (
<name@example.com>) are kept as written bynormalizeand other commands (previously rewritten as a broken relative link[name@example.com](name@example.com)) inlinekeeps the host document's frontmatter and drops the inlined document's frontmatter (previously the inlined frontmatter was pasted into the body as a---block and a laterinlinetook it over as the host's frontmatter)update --strict --dry-runanddelete --strict --dry-runreport schema violations and exit 2 like the real run (previously the preview skipped schema validation and reported success)update -c --dry-runreports'<key>' unchangedwhen the new content matches the document (previously reportedWould update)
iwes
Fixed
- Wiki embeds (
![[image.png]]) are kept as written when a document is formatted or updated by a code action (previously rewritten as Markdown images) - Link destinations containing spaces, such as links created by extract with a title-based key, are written as
<path with spaces>so they stay valid Markdown - Email autolinks (
<name@example.com>) are kept as written when a document is formatted (previously rewritten as a broken relative link) - Inline section code action no longer pastes the inlined document's frontmatter into the body as a
---block
iwec
Fixed
- Usage and error messages on Windows now show the command as
iwec(wasiwec.exe) iwe_queryupdate block operators treat a$sectionas one target, soexpect: 1passes and inserted content lands once below the section (previously applied to every block in the section when it was not the first block under its parent)iwe_inlineno longer pastes the inlined document's frontmatter into the body as a---block, so the host keeps its own frontmatterdry_runpreviews ofiwe_query,iwe_delete,iwe_rename,iwe_extract,iwe_inlineandiwe_attachreject schema violations like the real call (previously the preview skipped schema validation and reported success)
Library crates (liwe, diwe)
liwe
Changed
Inline::Imagenow carries aLinkTypeanddocument::Imagehas a newlink_typefield, so wiki embeds round-trip as![[...]]
Fixed
- Markdown writer wraps link and image destinations containing spaces or unbalanced parentheses in
<...> - Block update operators treat a
$sectionas one whole-tree target when it follows unselected sibling blocks (previously each block in the section was a separate target) - Email autolinks are read as
mailto:links and written back as<name@example.com>(previously read as a relative link to a document) - Section inline operation drops the inlined document's frontmatter instead of writing it into the host body