Edit name/amount on budget template entries (forward-only) #21

New issue

Closed

opened 2026-04-17 18:36:47 -06:00 by claude-code · 0 comments

claude-code commented

2026-04-17 18:36:47 -06:00

Collaborator

Problem

The budget template page only lets you add, delete, or edit notes on an entry. There is no way to edit the name or amount of an existing template entry. When a subscription price changes (e.g. Twitch $10.99 → $11.99) the only workaround is delete + re-add, which orphans Entry.id and breaks the MonthEntry.source_entry_id link on every existing month.

Goal

Add inline edit for name, amount, and notes on a budget template entry. The change must be forward-facing only: existing months (planning, active, closed) keep their snapshotted MonthEntry.planned, MonthEntry.name, MonthEntry.origin_name, and MonthEntry.origin_planned. Only months created after the edit pick up the new values, via the existing create_month snapshot path.

Design

Full spec: docs/superpowers/specs/2026-04-17-edit-budget-template-entries-design.md

Layout is variant A ("swap in place"): the read row's name/amount/actions cells are replaced by name/amount/notes inputs plus Save/Cancel buttons, in the same row slot. Notes fold into edit mode; empty notes render nothing. The existing POST /entries/{id}/notes route and its dedicated notes row are removed (notes now edited only through the save flow).

Out of scope

No schema change, no migration.
No "apply change to current month too" affordance.
No bulk edit, undo, or edit history.

## Problem The budget template page only lets you add, delete, or edit notes on an entry. There is no way to edit the **name** or **amount** of an existing template entry. When a subscription price changes (e.g. Twitch $10.99 → $11.99) the only workaround is delete + re-add, which orphans `Entry.id` and breaks the `MonthEntry.source_entry_id` link on every existing month. ## Goal Add inline edit for name, amount, and notes on a budget template entry. The change must be **forward-facing only**: existing months (planning, active, closed) keep their snapshotted `MonthEntry.planned`, `MonthEntry.name`, `MonthEntry.origin_name`, and `MonthEntry.origin_planned`. Only months created *after* the edit pick up the new values, via the existing `create_month` snapshot path. ## Design Full spec: `docs/superpowers/specs/2026-04-17-edit-budget-template-entries-design.md` Layout is variant A ("swap in place"): the read row's name/amount/actions cells are replaced by name/amount/notes inputs plus Save/Cancel buttons, in the same row slot. Notes fold into edit mode; empty notes render nothing. The existing `POST /entries/{id}/notes` route and its dedicated notes row are removed (notes now edited only through the save flow). ## Out of scope - No schema change, no migration. - No "apply change to current month too" affordance. - No bulk edit, undo, or edit history.