4 Commits

Include renames

Author	SHA1	Message	Date
Connor JohnstoneandClaude	79f287ed61	Fix calendar event fetching to use visible date range ... Moved event fetching logic from CalendarView to Calendar component to properly use the visible date range instead of hardcoded current month. The Calendar component already tracks the current visible date through navigation, so events now load correctly for August and other months when navigating. Changes: - Calendar component now manages its own events state and fetching - Event fetching responds to current_date changes from navigation - CalendarView simplified to just render Calendar component - Fixed cargo fmt/clippy formatting across codebase 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-01 18:31:51 -04:00
Connor JohnstoneandClaude	e55e6bf4dd	Clean up obsolete CalDAV environment variables ... ## Removed Obsolete Environment Variables: - `CALDAV_SERVER_URL` - provided by user login - `CALDAV_USERNAME` - provided by user login - `CALDAV_PASSWORD` - provided by user login - `CALDAV_TASKS_PATH` - not used in any features ## Kept with Intelligent Discovery: - `CALDAV_CALENDAR_PATH` - optional override, defaults to smart discovery ## Changes: ### Backend - Remove `CalDAVConfig::from_env()` method (not used in main app) - Add `CalDAVConfig::new()` constructor with credentials - Remove `tasks_path` field from CalDAVConfig - Update auth service to use new constructor - Update tests to use hardcoded test values instead of env vars - Update debug tools to use test credentials ### Frontend - Remove unused `config.rs` file entirely (frontend uses backend API) ## Current Authentication Flow: 1. User provides CalDAV credentials via login API 2. Backend creates CalDAVConfig dynamically from login request 3. Backend tests authentication via calendar discovery 4. Optional `CALDAV_CALENDAR_PATH` env var can override discovery 5. No environment variables required for normal operation This simplifies deployment - users only need to provide CalDAV credentials through the web interface, no server-side configuration required. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-31 19:48:13 -04:00
Connor JohnstoneandClaude	e21430f6ff	Implement complete event series endpoints with full CRUD support ... ## Backend Implementation - Add dedicated series endpoints: create, update, delete - Implement RFC 5545 compliant RRULE generation and modification - Support all scope operations: this_only, this_and_future, all_in_series - Add comprehensive series-specific request/response models - Implement EXDATE and RRULE modification for precise occurrence control ## Frontend Integration - Add automatic series detection and smart endpoint routing - Implement scope-aware event operations with backward compatibility - Enhance API payloads with series-specific fields - Integrate existing RecurringEditModal for scope selection UI ## Testing - Add comprehensive integration tests for all series endpoints - Validate scope handling, RRULE generation, and error scenarios - All 14 integration tests passing 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-30 13:21:44 -04:00
Connor JohnstoneandClaude	5cb77235da	Add comprehensive integration tests for all API endpoints ... - Add 9 integration tests covering all HTTP endpoints - Test authentication flow: login, verify, user info - Test calendar operations: create, delete, list events - Test event CRUD: create, update, delete, refresh - Add TestServer utility for automated server setup - Test both success and error scenarios (401, 400, 404) - Integration with real CalDAV server using .env credentials - Fix test module visibility by making handlers public - Move misplaced unit tests into proper test module - All tests passing: 7 unit + 9 integration = 16 total 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-30 12:17:09 -04:00