fire-planner/frontend
Viktor Barzin 7602f9040e
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
ui: drop restrictive step on monetary inputs + round NW autofill
step={1000}/step={10000} on £ inputs blocked any non-multiple value
from passing browser validation. Surfaced when the Wealthfolio
autofill landed `1050195.09` into the NW field — Chrome rejected
it: "the two nearest valid values are 1050000 and 1060000". Same
class as the n_paths bug from earlier today.

- Remove step on spending_gbp / nw_seed_gbp / savings_per_year_gbp /
  floor_gbp across What-If, ScenarioNew, ScenarioEdit. Default step=1
  (any positive integer).
- Round NW autofill to whole pounds (Math.round) since the user
  doesn't think in pence at this scale and the rounded value
  satisfies any integer step.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-10 00:34:09 +00:00
..
src ui: drop restrictive step on monetary inputs + round NW autofill 2026-05-10 00:34:09 +00:00
.gitignore frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
index.html frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
package-lock.json frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
package.json frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
tsconfig.app.json frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
tsconfig.json frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
tsconfig.node.json frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00
vite.config.ts frontend: scaffold Vite + React 19 + TS + Tailwind v4 + TanStack Query 2026-05-09 21:53:59 +00:00