feat(libra): guide expense description toward categorization #138

Merged
padreug merged 1 commit from feat/libra-expense-description-copy into dev 2026-06-25 20:11:54 +00:00
Owner

Addresses the near-term ask in #137.

What

Two copy changes in the Add-expense flow (src/modules/expenses/components/AddExpense.vue):

Step 1 — account selection. Added guidance to fall back to the "Other" account:

Select the account for this expense. Use the "Other" account if you're not sure.

Step 2 — Description field. Rewrote the placeholder to prompt for a categorization-friendly description, and removed the now-redundant helper line:

A detailed description of the purchase/invoice/bill, and what it was used for (event/project/etc)...

Why

Client feedback: we don't have a fixed category taxonomy yet, and the "category" in libra is really the account selected in Step 1 (AccountSelector). Steering unsure users to the Other account, plus a richer free-text description, lets us reconcile/recategorize later.

Scope notes

  • Copy-only. No logic, schema, type, or layout changes.
  • The Other account is assumed to already exist in the account hierarchy.
  • A separate PR will handle UI/layout tweaks (e.g. Amount + Currency on one row).
  • Formalizing an actual category taxonomy stays tracked in #137.

Refs #137

🤖 Generated with Claude Code

Addresses the near-term ask in #137. ## What Two copy changes in the Add-expense flow (`src/modules/expenses/components/AddExpense.vue`): **Step 1 — account selection.** Added guidance to fall back to the "Other" account: > Select the account for this expense. Use the "Other" account if you're not sure. **Step 2 — Description field.** Rewrote the placeholder to prompt for a categorization-friendly description, and removed the now-redundant helper line: > A detailed description of the purchase/invoice/bill, and what it was used for (event/project/etc)... ## Why Client feedback: we don't have a fixed category taxonomy yet, and the "category" in libra is really the **account** selected in Step 1 (`AccountSelector`). Steering unsure users to the **Other** account, plus a richer free-text description, lets us reconcile/recategorize later. ## Scope notes - Copy-only. No logic, schema, type, or layout changes. - The **Other** account is assumed to already exist in the account hierarchy. - A separate PR will handle UI/layout tweaks (e.g. Amount + Currency on one row). - Formalizing an actual category taxonomy stays tracked in #137. Refs #137 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Expand the expense Description helper text to prompt for a detailed
description (what the purchase/invoice/bill was + what it was used for:
event/project/etc) and point users to the "Other" account when none
of the existing accounts match.

Client feedback: with no fixed category taxonomy yet, a richer
description lets us reconcile/recategorize later even when the expense
lands on the Other account.

Refs aiolabs/webapp#137
padreug force-pushed feat/libra-expense-description-copy from d08949487f to 807f8200b1 2026-06-25 20:10:50 +00:00 Compare
padreug deleted branch feat/libra-expense-description-copy 2026-06-25 20:11:55 +00:00
Sign in to join this conversation.
No description provided.