feat(companion): UI Enhancements for Android and Extension

[dhairyashiil]

Screen.Recording.2026-01-05.at.6.20.21.PM.mov

and

Screen.Recording.2026-01-06.at.5.04.49.AM.mov

and

booking actions to React Query to enable auto relaod

Screen.Recording.2026-01-06.at.11.53.59.PM.mov

and

Screen.Recording.2026-01-06.at.11.55.03.PM.mov

---

Summary by cubic

Unified the bookings and event types UI across Android, iOS, and web with header dropdown filters, recurring series grouping with bulk actions, and cleaner empty states. Migrated booking data and actions to React Query for faster loads, pull‑to‑refresh, and reliable cache updates; fixed header button clipping on web.

• UI Improvements

  • Bookings (Android/iOS/web): Header dropdown for status (including Recurring) and inline event type dropdown; grouped recurring series with a dedicated list item and confirm/decline/cancel‑all; booking items and detail screen now use dropdown action menus.
  • Event Types (Android/iOS/web): Header menu for sort (alphabetical/newest/duration) and multi‑select filters (hidden/paid/seated/confirmation/recurring) with a badge and “Clear filters”; list items show badges and the public link path; improved empty states.
  • Headers: Added web‑only padding with HeaderButtonWrapper to prevent clipped buttons.

• Refactors

  • Unified Android implementations into shared components with a common DropdownMenu; removed platform‑specific files.
  • Added useEventTypeFilter across platforms; extended Header to support dropdown menus and filter badges.
  • Adopted React Query hooks for bookings: useBookingByUid, useRescheduleBooking, useUpdateLocation, useAddGuests, useMarkNoShow, useCancelBooking; deduplicated getUserProfile calls to reduce API traffic and speed up iOS.

^{Written for commit d76031c. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
cal	Ignored		Jan 6, 2026 6:32pm
cal-companion	Ignored	Preview	Jan 6, 2026 6:32pm
cal-eu	Ignored		Jan 6, 2026 6:32pm

[cubic-dev-ai]

5 issues found across 29 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="companion/utils/bookings-utils.ts">

<violation number="1" location="companion/utils/bookings-utils.ts:303">
P2: Duplicated filter logic: `remainingCount` uses the same filter as `upcomingBookings` but filters `sortedBookings` again. Use `upcomingBookings.length` instead to avoid redundant iteration and improve maintainability.</violation>
</file>

<file name="companion/app/(tabs)/(event-types)/index.tsx">

<violation number="1" location="companion/app/(tabs)/(event-types)/index.tsx:608">
P2: This condition is dead code. The early return at line 508 already handles `filteredEventTypes.length === 0 &amp;&amp; searchQuery.trim() !== &quot;&quot;` before the ScrollView is reached. Consider either removing the early return and keeping this ScrollView handling, or removing this unreachable branch.</violation>
</file>

<file name="companion/components/booking-list-item/RecurringBookingListItem.ios.tsx">

<violation number="1" location="companion/components/booking-list-item/RecurringBookingListItem.ios.tsx:23">
P2: The `onLongPress` prop is defined in the interface but never destructured or used in this iOS component. Unlike the base component which wires it to `TouchableOpacity.onLongPress`, this implementation silently ignores the callback. Consider either implementing the long-press handler or removing the prop from the interface.</violation>
</file>

<file name="companion/components/booking-list-item/RecurringBookingListItem.tsx">

<violation number="1" location="companion/components/booking-list-item/RecurringBookingListItem.tsx:128">
P2: The meeting link section duplicates the existing `MeetingLink` component from `BookingListItemParts.tsx`. Consider reusing that component instead of duplicating the logic, which improves maintainability and follows the codebase pattern established in `BookingListItem.tsx`.</violation>
</file>

<file name="companion/hooks/useEventTypeFilter.tsx">

<violation number="1" location="companion/hooks/useEventTypeFilter.tsx:171">
P2: Duplicated sorting logic. The same switch statement for sorting appears in two places (lines 88-102 and 159-173). Extract the sorting logic into a helper function to avoid duplication and improve maintainability.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

7 issues found across 46 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="companion/components/availability-list-item/AvailabilityListItem.tsx">

<violation number="1" location="companion/components/availability-list-item/AvailabilityListItem.tsx:104">
P2: The dropdown menu trigger is always rendered even when `scheduleActions` is empty. Consider conditionally rendering the dropdown only when there are actions available to avoid showing an empty menu.</violation>
</file>

<file name="companion/components/booking-list-screen/BookingListScreen.tsx">

<violation number="1" location="companion/components/booking-list-screen/BookingListScreen.tsx:347">
P2: Hardcoded strings in Alert.alert should use `t()` for localization. Consider using translation keys like `t(&#39;cancel_all_remaining&#39;)` and `t(&#39;cancel_all_remaining_confirmation&#39;, { count: group.remainingCount })`.</violation>

<violation number="2" location="companion/components/booking-list-screen/BookingListScreen.tsx:366">
P2: The try-catch around `cancelBookingMutation` is ineffective. React Query&#39;s `mutate` function doesn&#39;t throw - it uses the `onError` callback. The catch block will only handle synchronous errors (rare). Consider either removing the try-catch and relying solely on `onSuccess`/`onError`, or use `mutateAsync` if you need Promise-based error handling.</violation>
</file>

<file name="companion/components/booking-list-item/BookingListItem.tsx">

<violation number="1" location="companion/components/booking-list-item/BookingListItem.tsx:87">
P1: Missing `!isRejected` check in visibility condition. The `getBookingActions` utility already includes this check for reschedule actions. Consider using `actions.reschedule.visible &amp;&amp; actions.reschedule.enabled` for consistency, or add `&amp;&amp; !isRejected` to the condition.</violation>

<violation number="2" location="companion/components/booking-list-item/BookingListItem.tsx:94">
P1: Missing `!isRejected` check in visibility condition. Consider adding `&amp;&amp; !isRejected` to match the `getBookingActions` utility logic.</violation>

<violation number="3" location="companion/components/booking-list-item/BookingListItem.tsx:101">
P1: Missing `!isRejected` check in visibility condition. Consider adding `&amp;&amp; !isRejected` to match the `getBookingActions` utility logic.</violation>

<violation number="4" location="companion/components/booking-list-item/BookingListItem.tsx:140">
P1: Missing `!isRejected` check in visibility condition. Consider adding `&amp;&amp; !isRejected` to match the `getBookingActions` utility logic.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}