feat(activities): notification config on event create + edit #69
No reviewers
Labels
No labels
app:activities
app:chat
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!69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "notification-config"
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?
Summary
Exposes the buyer-notification fields the LNbits events extension
gained in v1.4.0 / v1.6.0 so organizers can opt buyers into email
text — without having to drop into the LNbits admin UI.
the create + edit form (collapsed by default to keep the
Lightning-only path uncluttered).
extra.email_notificationsandextra.nostr_notifications. Both off → backend doesn't sendanything (current behavior).
extra.notification_subject+extra.notification_bodyacceptorganizer-customized message text; empty falls through to the
extension's defaults.
extrais built by overlaying onto the existingevent.extraso unrelated fields the LNbits admin UI sets(
promo_codes,conditional,min_tickets) survive theround-trip through the webapp's create/edit.
This branch carries the v1.6.1 types/API alignment commit
(
620919d) as its foundational dependency. The siblingpayment-rails-patternPR carries the same commit; whichevermerges first lands it on
dev, the other rebases trivially.Test plan
npm run buildclean.on → submit. Confirm backend stores
extra.email_notifications = true.extra.notification_subjectset→ the field is pre-populated; saving with an unrelated change
preserves the subject.
promo_codesblock to → save from the webapp → confirm
promo_codessurvives in
extra.🤖 Generated with Claude Code