- Document current mobile logging limitations
- Propose phased approach for log collection and export
- Include privacy-first design considerations
- Outline implementation details and testing strategy
- Remove localLamport and lastSyncedLamport from all interfaces and models
- Simplify sync logic to use vector clocks exclusively for change tracking
- Remove Lamport-based conflict detection and sync status logic
- Update UI components to remove Lamport display elements
- Clean up backwards compatibility utilities
- Fix getVectorClock import error in sync.service.ts
- Remove debug alert from sync-safety-backup.service.ts
This simplifies the sync system by eliminating the dual tracking
mechanism that was causing complications and false conflicts.
Vector clocks provide better causality tracking for distributed sync.
* fix/multiple:
feat: improve reliably for repeatable tasks 2
feat: improve reliably for repeatable tasks
fix: avoid mutation
docs: add theme colors overview
fix: date pipe error with indonesian
build: fix docker build
fix: only filter out later today tasks for today list
fix: task detail panel not opening for tasks planned for later
- Document the root cause of the failing test
- Explain why setting Lamport values to 0 fixes the issue
- Provide verification of the fix logic
- Complete documentation of vector clock implementation work
- Fix add-tasks-for-tomorrow service to use dateStrToUtcDate() instead of new Date()
to prevent timezone issues in negative UTC offsets
- Add comprehensive timezone tests for date utility functions:
- getDateRangeForDay: test day boundaries, DST transitions, edge cases
- getDateTimeFromClockString: test clock parsing, local time preservation
- getDateRangeForWeek: enhance with timezone, DST, and boundary tests
- Document timezone behavior analysis and decisions
- Update CI to test in Los Angeles timezone in addition to Berlin
These changes ensure consistent date/time behavior across all timezones,
preventing issues like the day of week mismatch reported in issue #4653.
Fixes issue #4653 where the day of week displayed in Worklog and Quick History
views was incorrect for users in negative UTC offset timezones (e.g., America/Los_Angeles).
The bug was caused by using `new Date(dateStr)` which interprets YYYY-MM-DD format
strings as UTC, causing date shifts in negative timezone offsets.
Changes:
- Use `dateStrToUtcDate` utility in `formatDayStr` and `formatDayMonthStr` functions
- Add comprehensive timezone tests for date formatting utilities
- Fix string to number conversion in `autoFixTypiaErrors` for task entities
- Fix TypeScript type issues in multiple test files
- Add timezone test scripts to package.json for CI testing
The fix ensures dates are parsed correctly in the local timezone regardless
of the user's timezone offset.
- Add @super-productivity/plugin-api package with TypeScript definitions
- Define core plugin interfaces, types, and manifest structure
- Add plugin hooks system for event-driven architecture
- Create plugin API type definitions and constants
- Add documentation and development guidelines
