diff --git a/CHANGELOG.md b/CHANGELOG.md index 57e4b0d..adde633 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,23 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). --- +## [1.16.1] — 2026-11-02 + +### Fixed +- **Clear transaction edits wiped every transaction when the browser database didn't hold them.** + - **When:** FinLens had restored the transactions from `finlens-state.json` in a browser whose IndexedDB didn't have them (a new browser, or cleared site data). Its `transactions` store was empty, or held only some of them. + - **Cause:** `DataCleanup.clearEdits()` replaced the loaded transactions with the store's rows (`DB._getAllTransactions()` → `reconstituteTx(row, {})`). With an empty store, none were left. With a folder connected, `_finish()` then wrote the empty list to `finlens-state.json`. The next boot re-imported the folder's CSVs, so only transactions still in a CSV there came back. With a partial store, only the stored ones were kept, and rows memory didn't have were added. The bug was already on `master`. + - **Fix:** each loaded transaction is rebuilt without its edit, from the transaction itself (`_unedited()` in `views-cleanup.js`): its original description, category and type, no notes or plan link, and flags from the transaction rules. Transfers are then detected again. No transaction is dropped or added, and the state file gets all of them. The `transactions` store isn't written: filling an empty one is an import's job, and the state file holds every transaction. + - **Transactions now keep their CSV category and type.** `mkTx()` records `_originalCategories` and `_originalType`. `reconstituteTx()` carries them, `DB.loadAll()` takes them from the row, and `finlens-state.json` saves them. Before, an edit or transfer detection overwrote them, so nothing in memory could undo an edit. + - **Older files:** a transaction loaded from a `finlens-state.json` written by v1.16.0 or earlier, with no row in this browser, has no recorded category and type. If they were edited, or it was a transfer, they're worked out again from the description and amount, as an import does for checking and savings. A card's own Category column and Payment/Return type can't be recovered this way; Rebuild from your folder brings them back. + - **No IndexedDB:** without a database, the action only deleted the edit records, and the screen kept showing the edits until a reload. Now the values go back right away. +- **An import while edits existed saved the edits into IndexedDB.** `DB.importTransactions()` stored the category, type and flags that `mkTx()` showed, edits included. That happens on Rebuild from your folder, or when importing again after Clear transactions. Clear transaction edits then brought the edits back, and so did every boot from IndexedDB. The row now holds the CSV's values. Rows stored that way before keep the edits until Rebuild from your folder rewrites them. + +### Docs +- **CLAUDE.md:** §4.2 the two new fields and what a transaction keeps of its CSV row; §4.5 IndexedDB may not hold the loaded transactions; §10 a stored row holds the CSV's values; §20 Clear transaction edits. + +--- + ## [1.16.0] — 2026-11-02 ### Insights, Settings and the Welcome — Clarity redesign, part 4 diff --git a/CLAUDE.md b/CLAUDE.md index d9454c9..15d387d 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -59,7 +59,7 @@ Until then, this section is the rule. FinLens is a **single-origin, zero-build, vanilla JavaScript personal finance dashboard** that runs entirely in the browser. There is no server, no npm, no bundler, no framework, and no TypeScript. The entry point is `index.html`; everything else is a plain `.js` file in the `js/` folder. -**Current version:** v1.16.0 (updated in `index.html` footer, `README.md`, and `CHANGELOG.md` on every release). +**Current version:** v1.16.1 (updated in `index.html` footer, `README.md`, and `CHANGELOG.md` on every release). **What it does:** Imports CSV exports from a bank (checking + savings) and credit cards, parses and normalizes them into a unified transaction model, and renders a multi-tab financial dashboard with budgeting, debt tracking, savings forecasting, investment planning, and Claude-powered AI analysis. @@ -240,9 +240,14 @@ Transactions are created by `mkTx()` in `core.js` and never mutated directly — balance: null, // Always null — checking/savings exports have no running balance; balance is // computed from manually entered starting balance + transactions _originalDesc: string, // Immutable original CSV description + _originalCategories?: string[], // The CSV's category and type, before edits and transfer detection (v1.16.1). + _originalType?: string, // Set by mkTx(); DB.loadAll() takes them from the row; finlens-state.json keeps them. + // Missing on transactions from a file written by ≤v1.16.0 (see §20, Clear transaction edits) } ``` +**What a transaction keeps of its CSV row:** the description (`_originalDesc`), the category and type (`_originalCategories`, `_originalType`), the amount and the date. Notes and plan links (`link`) exist only in its edit, and the flags without an edit come from the transaction rules (`txRuleFlag()`). Together these rebuild it without its edit, from memory alone (`DataCleanup._unedited()`). + ### 4.3 The Account Model ```js @@ -317,6 +322,7 @@ loadStateFromFile() → found? - The `finlens_` prefix is applied automatically by `lsSet`/`lsGet`. - Don't call `saveStateToFile()` directly in hot paths — it's meant to be debounced via `_saveStateDebounced()` in `lsSet()`. - **Never use transactions straight from JSON.** `JSON.parse` turns `date` into a string and freezes the `category` getter. `loadStateFromFile()` rebuilds them with `reconstituteTx()`, as `DB.loadAll()` does; any new code that reads transactions from JSON must do the same. +- **IndexedDB may not hold the loaded transactions.** After a boot or restore from `finlens-state.json` (a new browser, cleared site data, `_restoreStateIfBrowserEmpty()`), the `transactions` store can be empty or hold only some of them. Code that changes the loaded transactions works from `State.transactions`, never by replacing them with the store's rows: a store row may only fill in a value a transaction lacks. Up to v1.16.0, Clear transaction edits replaced them and wiped every transaction (§20). - **Secrets never reach the file.** `saveStateToFile()` deliberately omits `apiKey`, and `loadStateFromFile()` strips it from files written by ≤v1.7.0 (moving it to browser storage if needed, then scheduling a re-save). Keep both behaviors when changing the serialized field list. --- @@ -693,6 +699,8 @@ The account id comes last on purpose: `migrate.js` relies on it to rename accoun **Re-upload safety:** IDs are final when they reach `DB.importTransactions()`, which reads the stored keys once and skips any ID it already holds. Re-uploading a file — or a newer export with rows appended — inserts only genuinely new rows. On each import it also deletes leftover copies from the old bug: a suffixed row whose base transaction is in the file but whose exact ID is not. Same-day identical rows always appear together in a bank export, so the file is authoritative for how many copies exist. The import results card reports these as "leftover duplicate copies removed". +**A stored row holds the CSV's values, never an edit.** `DB.importTransactions()` stores the transaction's `_originalDesc`, `_originalCategories` and `_originalType` as the row's `description`, `categories` and `type`, and the flags from the rules (`txRuleFlag()`), not what `mkTx()` shows. An import can run while edits exist (Rebuild from your folder, importing again after Clear transactions). Up to v1.16.0 the row took the edited category, type and flags, so they came back after Clear transaction edits. Rows stored that way by older versions keep them until Rebuild from your folder rewrites them. + --- ## 11. Transfer Detection @@ -963,7 +971,7 @@ Multiple credit card files can be loaded simultaneously. Each gets a unique `acc --- -*Last updated: v1.16.0 — 2026-11-02 (Trends, AI Analysis, Settings and the Welcome rebuilt: §3 file roles; §4.1 `cardDetails`, `sampleData`, AI history `model`; §6 tile tokens and Insights/Settings/Welcome components; §7 rule 7 covers Trends; §8 `loadFiles()` sample option; §9 `shellHero()`, `NO_RANGE_VIEWS`, ☰ → ×, JSON export/import buttons; §12 Settings tabs renamed, the Welcome, range label hidden on Trends and Settings; §13 quick analyses, tab state, history; §20 new fields, Use my own files, Export/Import JSON; §21 quick analyses send `AI_PROMPTS`; v1.15.0: Plan screens rebuilt: §3 file roles; §4.1 `debtPlan` and the Budget / Bucket / Debt / Scenario shapes; §6 `--teal-text` and Plan components; §7 rule 7 covers the Plan charts; §8 plan helpers (`payoffPlan()`, `growthByYear()` …); §9 plan form helpers, `simulatePayoff()` kept unused; §12 Plan titles, Forecast tabs, range label hidden on Plan screens; §13 debt balances in the summary; §20 Clear forecast scenarios / investment mix, Clear debts resets `debtPlan`; v1.14.0: Finances screens rebuilt: §4.1 Bill shape and `recurringConfirmed`; §6 new tokens and Finances components; §7 rule 7 inline SVG charts; §8 new aggregation helpers; §9 drawer, `TX_VIEWS`, SVG/heatmap/format helpers, bill helpers, removed renderers; §11 keywords re-run detection, `transferPairs()`, card payments; §12 page actions and Transactions pills; §20 Clear bills also clears spotted-charge choices; v1.13.0: Clarity redesign — §6 tokens and components; §9 theme, chart colors and app bar helpers; §12 app bar navigation replaces the sidebar and the emoji rule; §17 footer; §20 Data & Reset; v1.12.0: bank-neutral account codes, names, samples and docs; §22 `migrate.js` added; §3, §4, §5, §10, §18, §21 updated; v1.10.5: no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* +*Last updated: v1.16.1 — 2026-11-02 (Clear transaction edits works from memory: §4.2 `_originalCategories`, `_originalType` and what a transaction keeps of its row; §4.5 IndexedDB may not hold the loaded transactions; §10 a stored row holds the CSV's values; §20 Clear transaction edits; v1.16.0: Trends, AI Analysis, Settings and the Welcome rebuilt: §3 file roles; §4.1 `cardDetails`, `sampleData`, AI history `model`; §6 tile tokens and Insights/Settings/Welcome components; §7 rule 7 covers Trends; §8 `loadFiles()` sample option; §9 `shellHero()`, `NO_RANGE_VIEWS`, ☰ → ×, JSON export/import buttons; §12 Settings tabs renamed, the Welcome, range label hidden on Trends and Settings; §13 quick analyses, tab state, history; §20 new fields, Use my own files, Export/Import JSON; §21 quick analyses send `AI_PROMPTS`; v1.15.0: Plan screens rebuilt: §3 file roles; §4.1 `debtPlan` and the Budget / Bucket / Debt / Scenario shapes; §6 `--teal-text` and Plan components; §7 rule 7 covers the Plan charts; §8 plan helpers (`payoffPlan()`, `growthByYear()` …); §9 plan form helpers, `simulatePayoff()` kept unused; §12 Plan titles, Forecast tabs, range label hidden on Plan screens; §13 debt balances in the summary; §20 Clear forecast scenarios / investment mix, Clear debts resets `debtPlan`; v1.14.0: Finances screens rebuilt: §4.1 Bill shape and `recurringConfirmed`; §6 new tokens and Finances components; §7 rule 7 inline SVG charts; §8 new aggregation helpers; §9 drawer, `TX_VIEWS`, SVG/heatmap/format helpers, bill helpers, removed renderers; §11 keywords re-run detection, `transferPairs()`, card payments; §12 page actions and Transactions pills; §20 Clear bills also clears spotted-charge choices; v1.13.0: Clarity redesign — §6 tokens and components; §9 theme, chart colors and app bar helpers; §12 app bar navigation replaces the sidebar and the emoji rule; §17 footer; §20 Data & Reset; v1.12.0: bank-neutral account codes, names, samples and docs; §22 `migrate.js` added; §3, §4, §5, §10, §18, §21 updated; v1.10.5: no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* --- @@ -1011,7 +1019,7 @@ CSV files on disk are **never** modified. |---|---|---| | Clear transactions & accounts | Empties memory + `transactions`/`accounts` stores; turns `sampleData` off; with a folder connected, sets `csvAutoImportPaused` | Plans, edits, account labels/balances, `cardDetails`, settings | | Clear import log | Empties `import_log` | Everything else | -| Clear transaction edits | `txOverrides` + `tx_overrides` store; rebuilds loaded transactions with `reconstituteTx(raw, {})` | — | +| Clear transaction edits | `txOverrides` + `tx_overrides` store; rebuilds each loaded transaction without its edit, from memory (`_unedited()`), then `detectTransfers()` | Every loaded transaction; the `transactions` store as it is | | Clear budgets / bills / buckets / debts / forecast scenarios / investment mix / AI history | `State[key] = []` (`{}` for `investAlloc`; the empty value is `PLAN_ITEMS[i][2]`) + `lsSet`. Bills also resets `recurringConfirmed` (confirmed/dismissed spotted charges); Debts also resets `debtPlan` (`PLAN_ALSO`) | — | | Rebuild from folder | Clears transactions, accounts, import log, then `reloadFromDirHandle()` | Plans, edits, settings | | Disconnect folder | `forgetDataFolder()` — stops CSV auto-reload and state-file writes | Files on disk | @@ -1026,6 +1034,10 @@ CSV files on disk are **never** modified. - **Ending the pause:** `loadFiles()` clears it, so any import the user starts ends it: Reload or Reconnect, Rebuild, picking a folder or files. `forgetDataFolder()` (Disconnect) clears it too, and Start over removes it with the other keys. - **Browser storage only:** it lives in localStorage and IndexedDB `app_state`, never in `finlens-state.json`. Saves are debounced, so a backup file written before the pause ended could otherwise switch it back on. If browser storage is wiped, the folder re-imports as a recovery. - **Permission prompts need a fresh user gesture.** Destructive buttons use click-again-to-confirm (no `confirm()` dialog, which can outlast the ~5 s activation window), and actions ask for folder access before doing slow work. +- **Clear transaction edits works from the loaded transactions, never from IndexedDB** (v1.16.1). The `transactions` store can be empty after a restore from `finlens-state.json` (§4.5); up to v1.16.0 the action replaced the loaded transactions with its rows, so every transaction vanished and `_finish()` saved the empty list to the file. + - **The originals:** `_originalDesc`, `_originalCategories` and `_originalType` on the transaction (§4.2), flags from the rules. A store row only fills in the category and type when the transaction doesn't record them. + - **A file from ≤v1.16.0 with no row:** if a transaction's category or type was edited, or it was marked as a transfer, they are worked out again from the description and amount (`autoCategory()`, debit/credit by sign), as an import of a file without Category and Type columns does. That is exact for checking and savings; a card's own Category and Type (Sale/Payment/Return) can't be recovered. Rebuild from your folder gets them back. Worked-out values aren't recorded as `_original*`. + - **The `transactions` store isn't written.** When it's empty, the transactions aren't copied into it: filling it is an import's job (accounts, coverage, import log), and the state file, rewritten by `_finish()`, holds all of them. - **Start over must leave nothing behind.** It sets `State._resetInProgress` so a pending debounced save can't re-create the file, and `DB.open()` registers `onversionchange` so other tabs release the database. `idbGet`/`idbSet`/`idbDel` close their connections so `finlens_fs` can be deleted. - **Fields added in v1.16.0:** `cardDetails` and `sampleData` live in localStorage, IndexedDB `app_state` (`DB.loadAll()`) and `finlens-state.json`; Start over erases both with everything else. `cardDetails` is also in the JSON export. Importing your own files turns `sampleData` off after clearing the samples (`loadFiles()`). - `clearAllData()` is kept as a wrapper for `DataCleanup.startOver('archive')`. Up to v1.8.1 it only cleared `localStorage`, which IndexedDB and the state file then restored on reload. diff --git a/README.md b/README.md index bbe68b5..1781de5 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ > A zero-install, browser-native finance dashboard. Drop in your bank CSVs, get instant clarity on your money. -**Version:** v1.16.0 · **Stack:** Vanilla JS, HTML, CSS · **Install:** None +**Version:** v1.16.1 · **Stack:** Vanilla JS, HTML, CSS · **Install:** None --- @@ -261,4 +261,4 @@ See [CHANGELOG.md](CHANGELOG.md) for the full release history. --- -*FinLens v1.16.0 — Built for one person's finances, designed to be useful for anyone's.* +*FinLens v1.16.1 — Built for one person's finances, designed to be useful for anyone's.* diff --git a/index.html b/index.html index e06d24e..8b4be31 100644 --- a/index.html +++ b/index.html @@ -1164,7 +1164,7 @@
- + diff --git a/js/core.js b/js/core.js index 4b70890..320ab4b 100644 --- a/js/core.js +++ b/js/core.js @@ -618,6 +618,11 @@ function mkTx(o) { notes: ov.notes || '', balance: null, _originalDesc: o.description, + // The CSV's category and type, before edits and transfer detection (v1.16.1). + // "Clear transaction edits" restores them from the transaction itself, and the + // IndexedDB row stores them (DB.importTransactions()). finlens-state.json keeps them. + _originalCategories: [o.category], + _originalType: o.type, }; } diff --git a/js/db.js b/js/db.js index e7fd719..85d7189 100644 --- a/js/db.js +++ b/js/db.js @@ -28,6 +28,10 @@ function reconstituteTx(raw, ov) { notes: ov.notes || '', balance: null, _originalDesc: src, + // Carried over when the record has them: a transaction from mkTx() or from a + // finlens-state.json written since v1.16.1. DB.loadAll() adds them from the row. + _originalCategories: Array.isArray(raw._originalCategories) && raw._originalCategories.length ? [...raw._originalCategories] : undefined, + _originalType: raw._originalType || undefined, }; } @@ -213,20 +217,25 @@ const DB = { for (const tx of sorted) { if (existingIds.has(tx.id)) { skipped++; continue; } const d = tx.date instanceof Date ? tx.date : new Date(tx.date); + // The row holds the CSV's values; edits stay in txOverrides. mkTx() has already + // applied any edit to tx, and an import can run while edits exist (Rebuild from + // your folder, or importing again after Clear transactions). Up to v1.16.0 the row + // took the edited category, type and flags, so clearing the edits didn't undo them. + const src = tx._originalDesc || tx.description || ''; const storable = { id: tx.id, date: d, yearMonth: (typeof monthKey === 'function') ? monthKey(d) : d.toISOString().slice(0,7), account: tx.account, - type: tx.type, + type: tx._originalType || tx.type, schemaId, - description: tx._originalDesc || tx.description || '', + description: src, amount: tx.amount, - categories: Array.isArray(tx.categories) ? tx.categories : [tx.category || 'Other'], - isRecurring: !!tx.isRecurring, - isBill: !!tx.isBill, - isSubscription: !!tx.isSubscription, - _originalDesc: tx._originalDesc || tx.description || '', + categories: tx._originalCategories || (Array.isArray(tx.categories) ? tx.categories : [tx.category || 'Other']), + isRecurring: txRuleFlag(src, 'recurring'), + isBill: txRuleFlag(src, 'bill'), + isSubscription: txRuleFlag(src, 'subscription'), + _originalDesc: src, }; // Use a fresh transaction for each row to avoid transaction timeout @@ -380,7 +389,8 @@ const DB = { State.transactions = rawTxs .map(raw => { const ov = overridesMap.get(raw.id) || State.txOverrides[raw.id] || {}; - return reconstituteTx(raw, ov); + // The row holds the CSV's category and type (importTransactions()): the originals. + return reconstituteTx({ ...raw, _originalCategories: raw.categories, _originalType: raw.type }, ov); }) .sort((a, b) => b.date - a.date); diff --git a/js/views-cleanup.js b/js/views-cleanup.js index 6430403..7c1a75a 100644 --- a/js/views-cleanup.js +++ b/js/views-cleanup.js @@ -71,16 +71,22 @@ const DataCleanup = { this._done('good', 'Import log cleared.'); }, + // Puts every loaded transaction back to its CSV values, rebuilt from the loaded + // transactions themselves, so none is dropped or added (v1.16.1). Up to v1.16.0 it + // replaced them with IndexedDB's rows. That store is empty after a restore from + // finlens-state.json (a new browser, or cleared site data), so every transaction + // vanished, and _finish() then saved the empty list to the file. + // IndexedDB's transactions store is left as it is: it holds what imports put there. async clearEdits() { + const edits = State.txOverrides || {}; State.txOverrides = {}; lsSet('txOverrides', {}); await DB.clearStores(['tx_overrides']); - // Rebuild the loaded transactions without overrides so the change shows now. - if (DB._db && State.transactions.length) { - const raw = await DB._getAllTransactions(); - State.transactions = raw.map(r => reconstituteTx(r, {})).sort((a, b) => b.date - a.date); - detectTransfers(); - } + // A stored row only fills in what a transaction from an older finlens-state.json + // doesn't record. It never decides which transactions exist. + const rows = new Map((await DB._getAllTransactions()).map(r => [r.id, r])); + State.transactions = State.transactions.map(t => this._unedited(t, edits[t.id], rows.get(t.id))); + detectTransfers(); await this._finish('Transaction edits cleared.'); }, @@ -164,6 +170,48 @@ const DataCleanup = { /* ---------- helpers ---------- */ + // Transaction `t` as its import made it, without its edit `ov` (for clearEdits()). + // - Description: the kept original. Notes and the plan link live only in the edit. + // - Flags: from the transaction rules, as mkTx() sets them without an edit. + // - Category and type: recorded on the transaction since v1.16.1, else from its + // IndexedDB `row`. A transaction from an older finlens-state.json with no row has + // neither. If its category or type was edited, or it was marked as a transfer, they + // are worked out again from the description and amount, as an import of a file + // without Category and Type columns does. That is exact for checking and savings; + // a card's own Category and Type can't be recovered. detectTransfers() runs after. + _unedited(t, ov, row) { + ov = ov || {}; + const desc = t._originalDesc || t.description || ''; + const has = (c, ty) => Array.isArray(c) && c.length > 0 && !!ty; + let cats = t._originalCategories, type = t._originalType; + if (!has(cats, type) && row) { cats = row.categories; type = row.type; } + const known = has(cats, type); + if (!known) { + const edited = (ov.categories && ov.categories.length) || ov.category || ov.type; + cats = t.categories || []; + type = t.type; + if (edited || type === 'transfer') { + const keep = edited ? [] : cats.filter(c => c !== 'Transfer out' && c !== 'Transfer in'); + cats = keep.length ? keep : [autoCategory(desc)]; + type = t.amount < 0 ? 'debit' : 'credit'; + } + } + return reconstituteTx({ + id: t.id, date: t.date, amount: t.amount, + // No screen sets accountOverride, but older data can hold one: the row knows the + // account the transaction was imported into. + account: ov.accountOverride && row ? row.account : t.account, + description: desc, _originalDesc: desc, + categories: [...cats], type, + isRecurring: txRuleFlag(desc, 'recurring'), + isBill: txRuleFlag(desc, 'bill'), + isSubscription: txRuleFlag(desc, 'subscription'), + // Worked-out values aren't recorded as the CSV's: they stay a guess. + _originalCategories: known ? cats : undefined, + _originalType: known ? type : undefined, + }, {}); + }, + // Forget imported data in memory (the caller clears the matching DB stores). _dropImported() { State.transactions = []; diff --git a/js/views-settings.js b/js/views-settings.js index 59e7dd8..ee6af97 100644 --- a/js/views-settings.js +++ b/js/views-settings.js @@ -60,7 +60,7 @@ function _renderGeneralSettings(root) { /* ---- About (the Theme row is gone: light only for now) ---- */ appendHtml(root,`