calendar

Files

T

Connor Johnstone 13a752a69c Fix timezone bug in event drag-and-drop causing 4-hour offset

Events dragged to 4am-7am were appearing at 8am-11am due to double
timezone conversion. The issue was:

1. Frontend converted local time to UTC before sending to backend
2. Backend (after previous fix) converted "local time" (actually UTC) to UTC again
3. Result: double conversion causing 4+ hour shift in wrong direction

Solution: Remove frontend UTC conversion in drag-and-drop callback.
Let backend handle the local-to-UTC conversion consistently.

- Remove .and_local_timezone(chrono::Local).unwrap().to_utc() conversion
- Send NaiveDateTime directly as local time strings to backend
- Backend parse_event_datetime() now properly handles local-to-UTC conversion

Now drag-and-drop works correctly: drag to 4am shows 4am.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-09-03 16:21:24 -04:00

src

Fix timezone bug in event drag-and-drop causing 4-hour offset

2025-09-03 16:21:24 -04:00

styles

Implement dynamic 15-minute time grid density and remove final boundary

2025-09-03 15:35:50 -04:00

Cargo.toml

Rebrand application from 'Calendar App' to 'Runway'

2025-09-02 11:05:21 -04:00

favicon.ico

Add favicon and remove calendar.db from tracking