This issue covers the technical and visual planning phase for integrating wellness-specific milestones and daily tracking history into the existing Calendar Tab. Currently, the calendar only displays basic period dates; the goal is to expand this into a comprehensive health overview.
Goals
[ ] Data Mapping: Define the schema for how wellness events (symptoms, mood, and daily logs) are queried and displayed on a per-day basis.
[ ] UI Visualization: Design a set of icons/markers to represent different event types (e.g., a "pill" icon for birth control, a "heart" for symptoms) without cluttering the monthly view.
[ ] State Handling: Plan the UI transition so the calendar dynamically updates its markers based on whether the user is in Cycle Tracking or a general wellness mode.
Technical Requirements
Component: CalendarView.tsx
Data Source: Must integrate with existing HealthLog database tables.
Logic: Implementation of a getEventsForDate helper function to aggregate all user logs for a specific calendar cell.
This issue covers the technical and visual planning phase for integrating wellness-specific milestones and daily tracking history into the existing Calendar Tab. Currently, the calendar only displays basic period dates; the goal is to expand this into a comprehensive health overview.
Goals
[ ] Data Mapping: Define the schema for how wellness events (symptoms, mood, and daily logs) are queried and displayed on a per-day basis.
[ ] UI Visualization: Design a set of icons/markers to represent different event types (e.g., a "pill" icon for birth control, a "heart" for symptoms) without cluttering the monthly view.
[ ] State Handling: Plan the UI transition so the calendar dynamically updates its markers based on whether the user is in Cycle Tracking or a general wellness mode.
Technical Requirements
Component: CalendarView.tsx
Data Source: Must integrate with existing HealthLog database tables.
Logic: Implementation of a getEventsForDate helper function to aggregate all user logs for a specific calendar cell.