Note vault.adapter migration in 0.13.0 changelog

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Scott Tomaszewski 2026-05-31 08:53:27 -04:00
parent c10c3d8902
commit f17b6f6071

View file

@ -9,7 +9,8 @@
- Tightens type safety (removes `any`, narrows YAML/error handling) and moves remaining inline styles to `styles.css`
- Fixes a hover-preview event-listener leak: `BibleEventHandlers` is now a single plugin-owned `Component` whose `document` listeners and close-poll timer are registered through the Obsidian lifecycle (so they're released on unload) and tracked per document for correct pop-out behavior, instead of being re-created and leaked on every hover
- Surfaces a notification when opening a chapter fails instead of failing silently — e.g. opening the Bible without an ESV API token configured now explains that a token is needed (and points to the plugin settings) rather than doing nothing
- Known follow-ups (tracked in `FOLLOWUP.md`): file reads/writes should migrate to the `Vault`/`FileManager` APIs
- Migrates file access off `vault.adapter` onto the intended `Vault`/`FileManager` APIs: notes are created with `Vault.create()` and their frontmatter written via `FileManager.processFrontMatter()`, folders use `getAbstractFileByPath`/`createFolder`, deletions go through `FileManager.trashFile()` (respecting the user's trash settings), and paths are run through `normalizePath()`
- Known follow-ups (tracked in `FOLLOWUP.md`): ESV HTML is still rendered via `innerHTML`, and a couple of smaller cleanups remain
## 0.12.0