Repository navigation
Releases: zeiosmb/isokit
Releases · zeiosmb/isokit
Release list
0.1.1
Review-feedback release: addresses the Obsidian plugin review scan. No functional changes — rendered output is byte-identical to 0.1.0 (verified against the golden masters).
Changed
- No more
innerHTML. Rendered SVG is now parsed withDOMParserand appended as a real element; error blocks are built with Obsidian'screateEl, so error text travels astextContentand the DOM handles escaping. A test now asserts the built bundle never assignsinnerHTML. - Obsidian DOM helpers throughout. The zoom/legend control buttons use
createDiv/createElinstead ofdocument.createElement. - Typed renderer internals. The shape-kwargs type is a real interface instead of
Record<string, any>, clearing the scan'sno-unsafe-*warnings at their root. Removed dead code (unused constant and import) and an unneeded type assertion.
Notes for reviewers
The remaining scan warnings (node: imports and console output in src/cli.ts / src/io.ts) are isokit's Node CLI shell, which is not part of the plugin bundle — tests/obsidian.ts asserts the built main.js contains no node: requires.
0.1.0
Initial release of isokit for Obsidian.
What it does
Renders ```isokit code blocks — semantic YAML describing units, groups, flows, and annotations — in-note as isometric architecture diagrams (self-contained SVG, fonts embedded, no network). Works on desktop and mobile.
Features
- Semantic YAML input — describe the topology (units, groups, flows, annotations); layout, flow routing, numbered chips, and the legend are derived automatically. No coordinates needed.
- Interactive diagrams — zoom with the +/− buttons or ctrl/cmd+scroll, drag to pan, double-click to reset, and collapse the legend rail with the »/« toggle.
- Errors that help you fix the note — a failed render shows a structured error block citing the line inside your code block, what went wrong, and how to fix it.
- Quality is enforced — grid snapping, collision checks, axis-locked flow routes, and legend overflow are hard errors, not silent glitches.
Format
The full YAML contract lives in SPEC.md.