fix(events): let guests default to the card rail in the purchase dialog #146
No reviewers
Labels
No labels
app:activities
app:chat
app:chatelet
app:events
app:forum
app:libra
app:market
app:restaurant
app:tasks
app:wallet
app:webapp
bug
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aiolabs/webapp!146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/events-guest-default-rail"
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?
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:
selectedMethodIdwas 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 -bclean,vitest run src/modules/events26/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
Second commit on this branch:
e90c06fadds 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 (missingDate/Message-ID, image-only body — aiolabs/eventsfix/ticket-email-headers, v1.6.1-aio.9); the hint stays useful while sender reputation builds.