Unsupervised/unsupervised-scheduler
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Lesson booking: unified registration flow (single/weekly, questions, policy, payment) #3

New Issue
Closed
opened 2026-06-05 12:55:34 +00:00 by thatguygriff · 1 comment
thatguygriff commented 2026-06-05 12:55:34 +00:00
Owner
Copy Link
Copy Source

Rework private-lesson booking into the unified registration flow and gate confirmation on payment.

Spec: docs/features/lesson-booking.md

Scope

  • Extend {prefix}us_lessons: offering_id, recurrence (single/weekly), series_id, payment_id
  • Flow: pick offering -> pick slot (single) or weekly reservation -> answer questions -> accept current policies -> pay -> confirm + receipt
  • Weekly reservation = one series_id, N lesson rows, single full-term payment
  • Update POST /bookings body: offering_id, slot_id, recurrence, answers[], accepted_policy_version_ids[], payment data
  • Lesson reaches confirmed only once payment is paid (or comp)

Depends on

Offerings, Registration questions, Policies, Payments

Acceptance

  • Single and weekly bookings work end to end; tests under tests/Unit/Booking/ passing
Rework private-lesson booking into the unified registration flow and gate confirmation on payment. **Spec:** `docs/features/lesson-booking.md` ## Scope - Extend `{prefix}us_lessons`: `offering_id`, `recurrence` (`single`/`weekly`), `series_id`, `payment_id` - Flow: pick offering -> pick slot (single) or weekly reservation -> answer questions -> accept current policies -> pay -> confirm + receipt - Weekly reservation = one `series_id`, N lesson rows, single full-term payment - Update `POST /bookings` body: `offering_id`, `slot_id`, `recurrence`, `answers[]`, `accepted_policy_version_ids[]`, payment data - Lesson reaches `confirmed` only once payment is `paid` (or comp) ## Depends on Offerings, Registration questions, Policies, Payments ## Acceptance - Single and weekly bookings work end to end; tests under `tests/Unit/Booking/` passing
thatguygriff added the enhancement label 2026-06-05 12:55:34 +00:00
thatguygriff commented 2026-06-08 19:05:24 +00:00
Author
Owner
Copy Link
Copy Source

Closing as complete. Implemented and merged in PR #20 (registration flow: offering, questions, policy).

Closing as complete. Implemented and merged in PR #20 (registration flow: offering, questions, policy).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 enhancement
Extends an existing feature
 feature
New user-facing capability
 payments
Billing, Stripe, receipts, reporting
 security
Security vulnerability or hardening
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
thatguygriff (James Griffin-Allwood)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Unsupervised/unsupervised-scheduler#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?