vishiri/fantasia-sqlite-main

Fantasia Archive — SQLite in main process

Current state

• better-sqlite3 is a native Node dependency; access belongs in the main process (see stub and comments in src-electron/electron-main.ts).
• Temp / prototype DB path pattern: app.getPath('userData') + _faProjectTemp/ + database file (e.g. .fae extension in current experiments).

Principles

1. Never open arbitrary SQL from the renderer — expose narrow, validated operations via preload APIs if the UI needs data. If those APIs use main-process IPC, add channel names to electron-ipc-bridge.ts and register handlers in mainScripts/ipcManagement/register*Ipc.ts (see fantasia-electron-preload).
2. Paths: Use app.getPath('userData') (or other app.getPath variants) for per-user storage; create directories before opening the DB.
3. Native builds: better-sqlite3 must compile for the Electron/Node ABI used by the packaged app; verify yarn quasar:build:electron and packaged runs after upgrades.
4. Lifecycle: Open/close or pool connections deliberately; avoid leaking handles on window reload during dev.

Evolution

• When replacing the stub, add a dedicated module under src-electron/ (e.g. mainScripts/db/ or database/) and keep electron-main.ts thin.
• Plan migrations and backup/export consistent with the product’s “worldbuilding database” model (see fantasia-worldbuilding-domain).

TypeScript interfaces and types (types/)

• Put shared interface / type declarations in repository-root types/ (import with app/types/...). Prefer one domain-oriented module per feature area with brief JSDoc on exports (see types/I_appMenusDataList.ts). Do not add colocated <filename>.types.ts under src/, src-electron/, or .storybook-workspace/. Ambient augmentations for third-party modules also live under types/ and are loaded with a side-effect import from the owning boot file or src/stores/index.ts (see types/piniaModuleAugmentation.ts).
• For JavaScript (.js), TypeScript (.ts), Vue (.vue), and JSON (.json, .jsonc, .json5) files, enforce expanded multi-line object literals via ESLint (object-curly-newline + object-property-newline) and keep files auto-fixable with eslint --fix.