Gemini 3.8 Flash · Balanced
fix-handle-collective-multiple-host-on-destinationcalendar-cal-com
cal.com · TypeScript · S · 30–99 lines · 6 files
The normal review, with one generalist agent. Judge: Claude Haiku 5.5.
- Gold bugs found
- 4 of 9
- Comments published
- 4
- Comments matching a bug
- 4
- Comments not matching
- 0
- Cost of this PR
- $0.459
Published comments (4)
TypeError on mainHostDestinationCalendar when destinationCalendar is empty — An empty or null `evt.destinationCalendar` triggers an unhandled `TypeError` during Google Meet bookings. Use optional chaining on `mainHostDestinationCalendar?.integration` to safely fall back to Daily video.
Inverted condition for setting organization slug — Disabling billing drops `slug`, while enabling billing incorrectly assigns both `slug` and `requestedSlug`. Revert the condition on `slug` to check `!IS_TEAM_BILLING_ENABLED`.
destinationCalendar initialized to null drops team calendars — Collective bookings silently drop team members' calendars when the organizer lacks a destination calendar. Default `destinationCalendar` to an empty array instead of `null` so `push` can append `teamDestinationCalendars`.
Fallback calendar lookup searches by falsy externalCalendarId — Because `externalCalendarId` is falsy in the fallback branch, `selectedCalendar` always resolves to `undefined`. Default directly to `event.destinationCalendar?.[0]?.externalId` instead. **Also found in:** - `packages/app-store/googlecalendar/lib/CalendarService.ts:315-317`