ChinmayOnGithub / ChinmayOnGithub/tracker
[Architecture] Define canonical date-time serialization and timezone policy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 3
Description
Define one application-wide policy for instants, local dates, timezones, all-day events, recurring occurrences, API serialization, database storage, and client rendering. Audit all Calendar, Tasks, Activities, Today, Google Calendar, and offline queue code for inconsistent Date/string handling. Add shared helpers and regression tests covering timezone changes, midnight, DST, and cross-device rendering.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the Calendar, Tasks, Activities, Today, Google Calendar, and offline queue code for Date/string handling, then define the shared policy for instants, local dates, timezones, recurring occurrences, serialization, storage, and rendering. Done means shared helpers and regression tests cover timezone changes, midnight, DST, and cross-device rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, database, full-stack
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100