Frontend: More dayjs -> Temporal migration#9282
Conversation
MobileInstall the Dev Tool (iOS via TestFlight, iOS Simulator, or Android .apk) here. Scan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client.
Deep linksiOS Android Web (Vercel)View the Vercel web preview for this branch. Backend
Other
|
nabramow
left a comment
There was a problem hiding this comment.
Just one nit with the comment, otherwise everything seems to work as before!
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR is primarily an internal frontend refactor migrating date handling from dayjs to Temporal, with added abstractions and tests. The author explicitly noted that tested user flows showed no visible difference, and the changes do not introduce a new feature or a clearly noticeable bug fix for end users. While it may improve code consistency and future maintainability, it does not rise to the level of major technical infrastructure work that should appear in release notes. 🤖 Bot Debug InformationModel: |


localizeDurationfor consistency and so we can switch to browser APIs in the future.approxTimeDuration+approxDateDuration)There are still some public trip-related code using dayjs but I don't know how to test that so I didn't touch it.
Testing
Compared vercel preview and next: host requests, last active, local time, upcoming trips+stays on dashboard. Saw no difference.
Web frontend checklist
For maintainers