marcel/familienarchiv
1
0
Fork 0
Code Issues 110 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(relativeTime): guard against Invalid Date producing NaN strings
Some checks failed
CI / Unit & Component Tests (pull_request) Failing after 2m36s
Details
CI / OCR Service Tests (pull_request) Successful in 28s
Details
CI / Backend Unit Tests (pull_request) Failing after 2m53s
Details
CI / OCR Service Tests (push) Has been cancelled
Details
CI / Backend Unit Tests (push) Has been cancelled
Details
CI / Unit & Component Tests (push) Has started running
Details

Browse Source 
If a row ever receives a malformed uploadedAt (e.g. manual SQL migration,
backend regression), the helper now falls back to "vor 0 Minute(n)"
rather than rendering "vor NaN Tag(en)" to the user.

Addresses Nora's review suggestion.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit was merged in pull request #298.
This commit is contained in:
Marcel
2026-04-20 22:46:53 +02:00
parent 35303831f7
commit 6f3aa056a1
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
frontend/src/lib/relativeTime.spec.ts
View File

@@ -31,4 +31,11 @@ describe('relativeTimeDe', () => {
expect(relativeTimeDe(NOW, NOW)).toMatch(/0/);
expect(relativeTimeDe(NOW, NOW)).toMatch(/Minute/i);
});
it('falls back to 0 minutes when the input Date is invalid', () => {
const invalid = new Date('not-a-real-date');
// Never crash the UI if the backend ever ships a malformed uploadedAt.
expect(relativeTimeDe(invalid, NOW)).toMatch(/0/);
expect(relativeTimeDe(invalid, NOW)).toMatch(/Minute/i);
});
});