Fix calendar event fetching to use visible date range
	
		
			
	
		
	
	
		
	
		
			Some checks failed
		
		
	
	
		
			
				
	
				Build and Push Docker Image / docker (push) Failing after 1m7s
				
			
		
		
	
	
				
					
				
			
		
			Some checks failed
		
		
	
	Build and Push Docker Image / docker (push) Failing after 1m7s
				
			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>
This commit is contained in:
		| @@ -1,2 +1,2 @@ | ||||
| // Re-export from shared calendar-models library for backward compatibility | ||||
| pub use calendar_models::*; | ||||
| pub use calendar_models::*; | ||||
|   | ||||
| @@ -1,5 +1,5 @@ | ||||
| // RFC 5545 Compliant iCalendar Models | ||||
| pub mod ical; | ||||
|  | ||||
| // Re-export commonly used types   | ||||
| // pub use ical::VEvent; | ||||
| // Re-export commonly used types | ||||
| // pub use ical::VEvent; | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 Connor Johnstone
					Connor Johnstone