Booking matching chain: interest → selection/confirmation → notifications - #4
Merged
Conversation
/pool/[id] gets an express/withdraw-interest button for interpreters → expressInterest/withdrawInterest server actions writing booking_interests (RLS-scoped: own interpreter_id, booking must be open; idempotent on the unique violation). Expressing interest best-effort notifies the signer via the new createNotification helper (service-role, since notifications has no insert policy for authenticated). Signer-only/non-interpreter viewers see a note.
/bookings/[id] shows interest count + a 'Review & confirm' link while open, and the confirmed interpreters + their shared contact once confirmed. /bookings/[id]/select lists interested interpreters (safe-column public views) for multi-select → confirmInterpreters action: verifies ownership + that picks expressed interest, enforces team composition via isCompositionSatisfied, snapshots both parties' contacts into booking_confirmations (interpreter contact via admin client — signer can't read it under RLS), flips booking to confirmed, and notifies each confirmed interpreter.
/notifications lists the user's notifications (RLS own-row), newest first, with unread highlighting, relative timestamps, deep-links to the related booking/pool item, and a 'Mark all read' server action. /home becomes a simple hub: post a booking, browse the pool, and notifications with an unread count. Notification rows are created by the interest/confirm actions (feature 1 + 2) via the service-role helper.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds the core marketplace loop on top of the 006 booking surface.
/pool/[id](RLS-scoped writes tobooking_interests); best-effort notifies the signer./bookings/[id]/select, confirms viaconfirmInterpreters: ownership + interest checks, team-composition enforcement (isCompositionSatisfied), contact snapshot intobooking_confirmations(interpreter contact via admin client), booking →confirmed, notifies confirmed interpreters./bookings/[id]shows interest count / confirmed contacts.notificationshas no insert policy);/notificationslists them with unread state + mark-all-read;/homeis now a hub (post / pool / notifications with unread count).No DB/schema changes — uses the existing
booking_interests/booking_confirmations/notificationstables + RLS. Verified: typecheck (web+mobile), lint, 36 tests, web build (new/bookings/[id]/select+/notificationsroutes).Out of scope (later): partial/multi-slot selection UX, email/push delivery of notifications, the OQ4 timezone handling, the
/auth/confirmprefetch hardening.