Calendar functionality #654

Activity

1. ngoiyaeric commented on Jun 8, 2026

   

   ngoiyaeric

   on Jun 8, 2026

   CollaboratorAuthor

   More actions

   @coderabbitai plan to improve the functionality for geospatial context. Such as using the calendar icon at a location for rendezvous.

   👀React with 👀1Reacted by coderabbitai
2. coderabbitai commented on Jun 8, 2026

   

   coderabbitaibot

   on Jun 8, 2026 – with coderabbitai

   Contributor

   More actions

   Coding Plan

   Summary

   • Fix the untracked migration by registering 0001_add_calendar_notes in the Drizzle journal with a corresponding snapshot file
   • Add database indexes on user_id, date, (user_id, date), and chat_id columns to support the query patterns in getNotes
   • Keep changes minimal and infrastructure-focused, avoiding feature additions (delete, edit UI, loading states) that are not explicitly requested

   Implementation Steps

   Phase 1: Fix Migration Tracking

   The 0001_add_calendar_notes.sql migration exists but is not registered in the Drizzle migration journal, which could cause deployment issues where the migration is re-run or skipped unexpectedly.

   Register Calendar Notes Migration in Journal

   Update the migration journal to track the existing calendar_notes migration and ensure Drizzle's migrator recognizes it as applied.

   • Add entry for 0001_add_calendar_notes to drizzle/migrations/meta/_journal.json with appropriate timestamp and hash
   • Create drizzle/migrations/meta/0001_snapshot.json capturing the schema state after the calendar_notes table addition
   • Verify the migration entry format matches the existing 0000_sweet_metal_master entry structure

   🤖 Prompt for AI agents

   Register the existing `0001_add_calendar_notes.sql` migration in the Drizzle
   migration journal so the migrator correctly recognizes it as applied.
   
   - In `drizzle/migrations/meta/_journal.json`, add a new entry for
   `0001_add_calendar_notes` with an appropriate timestamp and hash, following the
   exact format of the existing `0000_sweet_metal_master` entry
   - Create `drizzle/migrations/meta/0001_snapshot.json` that captures the schema
   state after the `calendar_notes` table has been added
   - Ensure the new journal entry structure (field names, ordering, formatting)
   mirrors the existing entry exactly
   

   Phase 2: Add Database Indexes for Performance

   The calendar_notes table lacks indexes on frequently queried columns, which will cause performance degradation at scale since every getNotes call performs a full table scan.

   Task 1: Create Index Migration

   Add a new Drizzle migration to create indexes on the calendar_notes table for the primary query patterns.

   • Create new migration file in drizzle/migrations/ (e.g., 0002_calendar_notes_indexes.sql)
   • Add index on user_id column for user-scoped queries
   • Add index on date column for date-range filtering
   • Add composite index on (user_id, date) to optimize the canonical query pattern used by getNotes
   • Add index on chat_id for chat-scoped note retrieval

   Task 2: Update Schema with Index Definitions

   Add index definitions to the Drizzle schema so future migrations stay in sync.

   • Update lib/db/schema.ts to include index definitions on the calendarNotes table using Drizzle's index syntax
   • Ensure indexes match those created in the migration file

   Task 3: Register Index Migration in Journal

   Track the new index migration properly in the Drizzle migration system.

   • Add entry for the new index migration to drizzle/migrations/meta/_journal.json
   • Create corresponding snapshot file in drizzle/migrations/meta/

   🤖 Prompt for AI agents

   Add database indexes to the `calendar_notes` table to eliminate full table scans
   on `getNotes` queries, then register the migration in the Drizzle journal.
   
   **Create the migration file:**
   - Create `drizzle/migrations/0002_calendar_notes_indexes.sql`
   - Add an index on `user_id` for user-scoped queries
   - Add an index on `date` for date-range filtering
   - Add a composite index on `(user_id, date)` to optimize the canonical query
   pattern used by `getNotes`
   - Add an index on `chat_id` for chat-scoped note retrieval
   
   **Update the schema:**
   - In `lib/db/schema.ts`, add index definitions on the `calendarNotes` table
   using Drizzle's index syntax
   - Ensure all index definitions exactly match those defined in the migration file
   
   **Register in the journal:**
   - Add an entry for `0002_calendar_notes_indexes` to
   `drizzle/migrations/meta/_journal.json`
   - Create the corresponding `drizzle/migrations/meta/0002_snapshot.json` snapshot
   file
   

   Research

   The calendar system is built around CalendarNotepad (components/calendar-notepad.tsx), which provides a date-based note-taking interface with location tagging via map integration. Server actions in lib/actions/calendar.ts handle note CRUD operations using Drizzle ORM against the calendar_notes table defined in lib/db/schema.ts. Visibility is managed by CalendarToggleProvider (components/calendar-toggle-context.tsx), with toggle buttons in both the desktop header and mobile icons bar. The system supports chat association for AI context by injecting role: 'data' messages when notes are linked to a chat session.

   ---

   🚀 Next Steps

   🤖 All AI agent prompts combined

   Task: 1
   
   Register the existing `0001_add_calendar_notes.sql` migration in the Drizzle
   migration journal so the migrator correctly recognizes it as applied.
   
   - In `drizzle/migrations/meta/_journal.json`, add a new entry for
   `0001_add_calendar_notes` with an appropriate timestamp and hash, following the
   exact format of the existing `0000_sweet_metal_master` entry
   - Create `drizzle/migrations/meta/0001_snapshot.json` that captures the schema
   state after the `calendar_notes` table has been added
   - Ensure the new journal entry structure (field names, ordering, formatting)
   mirrors the existing entry exactly
   ===============================================================================
   
   Task: 2
   
   Add database indexes to the `calendar_notes` table to eliminate full table scans
   on `getNotes` queries, then register the migration in the Drizzle journal.
   
   **Create the migration file:**
   - Create `drizzle/migrations/0002_calendar_notes_indexes.sql`
   - Add an index on `user_id` for user-scoped queries
   - Add an index on `date` for date-range filtering
   - Add a composite index on `(user_id, date)` to optimize the canonical query
   pattern used by `getNotes`
   - Add an index on `chat_id` for chat-scoped note retrieval
   
   **Update the schema:**
   - In `lib/db/schema.ts`, add index definitions on the `calendarNotes` table
   using Drizzle's index syntax
   - Ensure all index definitions exactly match those defined in the migration file
   
   **Register in the journal:**
   - Add an entry for `0002_calendar_notes_indexes` to
   `drizzle/migrations/meta/_journal.json`
   - Create the corresponding `drizzle/migrations/meta/0002_snapshot.json` snapshot
   file
   

   💡 Iterate on the plan with: `@coderabbitai` <feedback>

   Example Feedback
   - `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
   - `@coderabbitai` For design choice 1 go ahead with option 3 and replan.
   

   ---

   💬 Have feedback or questions? Drop into our discord!
3. ngoiyaeric commented on Jun 8, 2026

   

   ngoiyaeric

   on Jun 8, 2026

   CollaboratorAuthor

   More actions

   @coderabbitai the system code for the calendar function is not working right now. I need more pre-database utility like notes on locations and reminders with notifications.

   👀React with 👀1Reacted by coderabbitai
4. coderabbitai commented on Jun 8, 2026

   

   coderabbitaibot

   on Jun 8, 2026 – with coderabbitai

   Contributor

   More actions

   🧩 Analysis chain

   🏁 Script executed:

   #!/bin/bash
   # Inspect key calendar-related files
   echo "=== Calendar Notepad Component ==="
   fd "calendar-notepad" --type f | head -5
   
   echo "=== Calendar Actions ==="
   fd "calendar" lib --type f 2>/dev/null | head -10
   
   echo "=== DB Schema ==="
   fd "schema.ts" lib --type f | head -5
   
   echo "=== Migration files ==="
   fd "." drizzle --type f | sort
   
   echo "=== Calendar toggle context ==="
   fd "calendar-toggle" --type f | head -5
   
   echo "=== Any notification/reminder files ==="
   fd "notif\|remind" --type f | head -10
   
   echo "=== Any geospatial/location files ==="
   fd "geo\|location\|map" --type f | head -20

   Length of output: 1142

   ---

   🏁 Script executed:

   #!/bin/bash
   echo "=== calendar-notepad.tsx ==="
   cat components/calendar-notepad.tsx 2>/dev/null || fd "calendar-notepad" --exec cat {}
   
   echo "=== lib/actions/calendar.ts ==="
   cat lib/actions/calendar.ts 2>/dev/null
   
   echo "=== lib/db/schema.ts ==="
   cat lib/db/schema.ts 2>/dev/null
   
   echo "=== drizzle journal ==="
   cat drizzle/migrations/meta/_journal.json 2>/dev/null
   
   echo "=== existing migrations ==="
   ls drizzle/migrations/*.sql 2>/dev/null | xargs -I{} sh -c 'echo "--- {} ---"; cat {}'

   Length of output: 20333

   ---

   🏁 Script executed:

   #!/bin/bash
   # Check where lib/types is defined to get CalendarNote type shape
   fd "types" lib --type f | head -10
   cat lib/types.ts 2>/dev/null || fd "types" lib --exec cat {} \; 2>/dev/null | head -100

   Length of output: 443

   ---

   🏁 Script executed:

   #!/bin/bash
   # Check how providers are composed in the app layout
   fd "layout" app --type f | head -5
   cat app/layout.tsx 2>/dev/null || fd "layout.tsx" app --exec cat {} \; 2>/dev/null | head -60
   # Check if there's a root providers component
   fd "providers" components --type f | head -5
   cat components/providers.tsx 2>/dev/null

   Length of output: 4749

   ---

   🏁 Script executed:

   #!/bin/bash
   # Check lib/types for CalendarNote shape
   fd "types" lib --type f | head -5
   cat lib/types.ts 2>/dev/null | head -80
   fd "types.ts" lib --exec cat {} \; 2>/dev/null | head -80

   Length of output: 427

   ---

   🏁 Script executed:

   #!/bin/bash
   echo "=== Find types files ==="
   fd "types" --type f | grep -v "node_modules" | grep -v ".next"
   
   echo "=== Search for CalendarNote type definition ==="
   rg "CalendarNote" --type ts -n -C2 | head -60
   
   echo "=== Search for NewCalendarNote ==="
   rg "NewCalendarNote" --type ts -n -C2 | head -30

   Length of output: 5720

   ---

   🏁 Script executed:

   #!/bin/bash
   echo "=== lib/types/index.ts ==="
   cat lib/types/index.ts
   
   echo "=== drizzle/migrations/meta/0000_snapshot.json (first 80 lines for format reference) ==="
   head -80 drizzle/migrations/meta/0000_snapshot.json

   Length of output: 4134

   ---

   ---

   Now I have everything. Here is the complete, implementation-ready plan:

   Task: Fix broken calendar + add pre-DB local state, location notes & reminders

   • Phase 1 — Register 0001_add_calendar_notes in Drizzle journal + create snapshot
   • Phase 2 — New migration 0002_add_calendar_reminders.sql + journal + snapshot
   • Phase 3 — Update lib/types/index.ts — add reminder fields to CalendarNote
   • Phase 4 — Update lib/db/schema.ts — add reminder columns + indexes
   • Phase 5 — Create lib/hooks/use-local-notes.ts — localStorage pre-DB layer
   • Phase 6 — Create lib/hooks/use-reminders.ts — browser Notification API scheduler
   • Phase 7 — Create components/reminder-notification-provider.tsx — permission + polling
   • Phase 8 — Update lib/actions/calendar.ts — add getUpcomingReminders + markReminderTriggered
   • Phase 9 — Update components/calendar-notepad.tsx — fix "use client" dup, add reminder picker, location display, optimistic saves, initialLocation prop
   • Phase 10 — Update app/layout.tsx — add <ReminderNotificationProvider>

   statement-breakpoint

   ALTER TABLE "calendar_notes" ADD COLUMN IF NOT EXISTS "reminder_triggered" boolean DEFAULT false NOT NULL;
   --> statement-breakpoint
   CREATE INDEX IF NOT EXISTS "calendar_notes_user_id_idx" ON "calendar_notes" ("user_id");
   --> statement-breakpoint
   CREATE INDEX IF NOT EXISTS "calendar_notes_date_idx" ON "calendar_notes" ("date");
   --> statement-breakpoint
   CREATE INDEX IF NOT EXISTS "calendar_notes_user_date_idx" ON "calendar_notes" ("user_id", "date");
   --> statement-breakpoint
   CREATE INDEX IF NOT EXISTS "calendar_notes_reminder_time_idx" ON "calendar_notes" ("reminder_time") WHERE reminder_time IS NOT NULL AND reminder_triggered = false;

   
   **Update `drizzle/migrations/meta/_journal.json`** — add a third entry:
   ```json
   {
     "idx": 2,
     "version": "5",
     "when": 1750358700000,
     "tag": "0002_add_calendar_reminders",
     "breakpoints": true
   }
   

   Create drizzle/migrations/meta/0002_snapshot.json — copy structure from 0001_snapshot.json, use a new UUID for "id", set "prevId" to the UUID used in 0001_snapshot.json, and add reminder_time (timestamp with time zone, nullable) and reminder_triggered (boolean, notNull, default false) to the calendar_notes columns, plus add the four index entries under calendar_notes.indexes.
   -->

   ---

   💡 For code changes across multiple files, use @coderabbitai plan in an issue comment