Repository navigation
Releases
Releases · quartz-community/obsidian-plugin-excalidraw
v1.1.1
Patch Changes
- df64ea8: Uses Quartz's own
preactinstead of bundling a second copy (noExternalin the build overrode the externals). Components now share one Preact instance with Quartz and other plugins, so hooks and context work across them, and the bundle is smaller.
v1.1.0
Minor Changes
- afc0c41: Drawings follow the site's publish rules (quartz-community/bases-page#11). A drawing stored as Markdown (
.excalidraw.md) gets its page only when the site's filters publish its note, and the page carries the note's frontmatter (publish,draft,password, …), so with Quartz 5.1 explicit-publish, drafts and encrypted-pages treat it like a note. The plugin's own filter keeps the drawing pages it generates (Quartz 5.1 runs the filters on them). A.excalidraw(JSON) drawing has no frontmatter: with explicit-publish it is published when a published note links to it.
v1.0.2
Patch Changes
- 5862c1c: Excalidraw pages now carry the path of their drawing file (
filePath/relativePath) instead of a made-up<name>.excalidraw.md. Base views (bases-page) list drawings withfile.path,file.ext(excalidraw, ormdfor a drawing stored as.excalidraw.md),file.folderandfile.inFolder()as Obsidian does, the content index records the real file path, and drawing pages get their generated social image. - 81f33ed: Bundles
@quartz-community/utils1.1.0: a short wikilink to an Obsidian folder note ([[Topic]]forTopic/Topic.md) reaches the folder page, and anchors to headings use the same slug as heading ids.github-sluggeris no longer a dependency of this plugin.
v1.0.1
Patch Changes
- dbe786c: Releases are published from GitHub Actions with npm trusted publishing, so each version on npm now carries provenance linking it to the commit and workflow that built it. No changes to the package itself.
v1.0.0
Major Changes
-
Stable 1.0 release. All
@quartz-community/*dependencies now use^1.0.0ranges.Pre-1.0 caret ranges pinned the minor version (
^0.2.1means>=0.2.1 <0.3.0), so
published fixes to shared packages could never be resolved by dependents. Moving the
ecosystem to 1.0 makes caret ranges behave conventionally.
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.