Negative points balances render inconsistently across ledgers #122

New issue

Closed

opened 2026-08-18 10:45:23 +00:00 by nalum · 1 comment

nalum commented

2026-08-18 10:45:23 +00:00

Owner

From the surface parity report (2026-08-18), defect 13.

Web has 3 balance ledgers: PointsChip and Rewards clamp at 0, Today.tsx:419 does not. Android mirrors this: only the header chip (TopBar.kt:182) clamps. A member whose spends exceed claims sees "-5 points" on one board and "0" in the header, on both platforms.

Fix: one shared balance function per surface, one clamping decision. See also the consolidation issues for shared points formatters.

From the surface parity report (2026-08-18), defect 13. Web has 3 balance ledgers: `PointsChip` and Rewards clamp at 0, `Today.tsx:419` does not. Android mirrors this: only the header chip (`TopBar.kt:182`) clamps. A member whose spends exceed claims sees "-5 points" on one board and "0" in the header, on both platforms. Fix: one shared balance function per surface, one clamping decision. See also the consolidation issues for shared points formatters.

nalum added the

bug

android

web

labels

2026-08-18 10:45:23 +00:00

nalum referenced this issue

2026-08-18 11:22:44 +00:00

Order of work for the open backlog (#107–#136) #137

nalum referenced this issue from a commit

2026-08-18 14:07:53 +00:00

refactor(web): one points module, one clamped balance

nalum referenced this issue

2026-08-18 14:08:11 +00:00

refactor: web shared entity components — kill the render forks #145

nalum referenced this issue from a commit

2026-08-18 14:18:35 +00:00

refactor(android): one clamped balance, one wording for points

nalum referenced this issue

2026-08-18 14:18:52 +00:00

refactor: Android shared entity components — port the web's shapes #146

nalum commented

2026-08-18 16:47:10 +00:00

Author

Owner

Delivered across PR #145 (web) and PR #146 (Android), both merged. Ruling recorded: a display balance is what you can spend, so every ledger clamps at 0 — web through points.ts balanceOf, Android through RewardsRepository.balanceOf, with the zero-balance strip hidden. The TUI's bounty math was fixed in PR #147's shared rows.