fix(events): let guests default to the card rail in the purchase dialog #146

Merged
padreug merged 1 commit from fix/events-guest-default-rail into dev 2026-09-08 13:24:41 +00:00
Owner

Found while running the guest purchase through the demo UI after #144: an anonymous buyer opening "Test Event" (Lightning + Card on offer) saw Proceed (Lightning) preselected, although the default-rail watcher is meant to prefer Card for guests.

Cause: selectedMethodId was initialised to 'lightning', so the watcher's "keep the current selection" guard matched immediately and the guest preference never applied. It now starts empty and is reset to empty on close, so every open re-evaluates: guests land on Card when it exists, everyone else on the first enabled rail.

One-file change; vue-tsc -b clean, vitest run src/modules/events 26/26.

Not blocking the production run (that event will be card-only via the new Payment methods checkboxes), but it matters for any event that keeps both rails.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EYwoAkZZmXMMmaBp4WGUBo

Found while running the guest purchase through the demo UI after #144: an anonymous buyer opening "Test Event" (Lightning + Card on offer) saw **Proceed** (Lightning) preselected, although the default-rail watcher is meant to prefer Card for guests. Cause: `selectedMethodId` was initialised to `'lightning'`, so the watcher's "keep the current selection" guard matched immediately and the guest preference never applied. It now starts empty and is reset to empty on close, so every open re-evaluates: guests land on Card when it exists, everyone else on the first enabled rail. One-file change; `vue-tsc -b` clean, `vitest run src/modules/events` 26/26. Not blocking the production run (that event will be card-only via the new Payment methods checkboxes), but it matters for any event that keeps both rails. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01EYwoAkZZmXMMmaBp4WGUBo
`selectedMethodId` started as 'lightning', so the "keep the current
selection" guard in the default-rail watcher always found a match and the
guest preference for fiat never applied — verified on demo, where an
anonymous buyer saw "Proceed" (Lightning) preselected with Card on offer.
Start empty and reset to empty on close so each open re-evaluates:
guests land on Card when it exists, everyone else on the first enabled
rail, exactly as the comment already promised.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EYwoAkZZmXMMmaBp4WGUBo
padreug deleted branch fix/events-guest-default-rail 2026-09-08 13:24:42 +00:00
Author
Owner

Second commit on this branch: e90c06f adds a red "check your spam folder" hint under the email field (en/es/fr), after a tester's ticket email was spam-foldered. Root cause is on the mailer side (missing Date/Message-ID, image-only body — aiolabs/events fix/ticket-email-headers, v1.6.1-aio.9); the hint stays useful while sender reputation builds.

Second commit on this branch: `e90c06f` adds a red "check your spam folder" hint under the email field (en/es/fr), after a tester's ticket email was spam-foldered. Root cause is on the mailer side (missing `Date`/`Message-ID`, image-only body — aiolabs/events `fix/ticket-email-headers`, v1.6.1-aio.9); the hint stays useful while sender reputation builds.
Sign in to join this conversation.
No description provided.