obsidian-data-handling

# Obsidian Data Handling ## Overview Data management patterns for Obsidian plugins: plugin config with loadData/saveData, vault file I/O, frontmatter parsing via metadataCache, handling renames and deletes, cross-device sync considerations, and IndexedDB fallback for large datasets. ## Prerequisites - Working Obsidian plugin (`export default class extends Plugin`) - Understanding of Obsidian's `Vault` and `MetadataCache` APIs - TypeScript compilation configured ## Instructions ### Step 1: Plugin Config with loadData / saveData Obsidian stores plugin data in `.obsidian/plugins/<plugin-id>/data.json`. Use `loadData()` and `saveData()` — never read that file directly. ```typescript interface PluginConfig { version: number; apiEndpoint: string; syncInterval: number; excludedFolders: string[]; } const DEFAULT_CONFIG: PluginConfig = { version: 1, apiEndpoint: 'https://api.example.com', syncInterval: 300, excludedFolders: [], }; export default class DataPlugin extends Plugin { config: PluginConfig; async onload() { await this.loadConfig(); } async loadConfig() { const saved = await this.loadData(); this.config = Object.assign({}, DEFAULT_CONFIG, saved); // Migrate from older config versions if (this.config.version < 1) { this.config.excludedFolders = []; this.config.version = 1; await this.saveConfig(); } } async saveConfig() { await this.saveData(this.config); } } ``` `loadData()` returns `null...