You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4d83110
Browse filesBrowse the repository at this point in the historyBrowse files
Fix a bundle regression, silent save failures and duplicate dates
Quality pass. Three real bugs, one of which I introduced last change.
The report sheet was imported eagerly by App, and it pulls in the
Firestore SDK — which silently undid the entry-chunk split and took
first load from 103 KB back to 236 KB gzipped. A signed-out visitor was
downloading the whole database SDK again. It's lazy now, like Home, and
the entry chunk is back to 103 KB.
No write path handled failure. Firestore applies a write locally and
rolls it back if the server rejects it, so a refused save looked like
the date appearing and then vanishing by itself, with nothing said.
Failures now surface as a dismissable alert.
Double-tapping "add it" created duplicate dates. The first fix for this
was wrong and the test caught it: setSaving(true) lands on the next
render, so three taps in one tick all read false. It uses a ref now,
which updates synchronously — verified three taps produce one date.
Also: "back to today" on the calendar, appearing only once you've paged
away from the current month, and dropped the "what gets sent with it"
disclosure from the report form.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments