feat: back Buzz Events with Zoom Meetings#288
Open
harshtandiya wants to merge 2 commits into
Open
Conversation
…tration) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
harshtandiya has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
harshtandiya has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
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
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.
What
Lets a Buzz Event be backed by a Zoom Meeting (in addition to the existing Webinar path) — create it from the event, keep it in sync, and register ticket holders so they get a join URL.
Depends on bwhtech/zoom_integration#17 (Zoom Meeting doctype +
meetingfield on the registration doctype). Tests here need that branch on the same bench.Changes
install.py— one new custom fieldzoom_meeting(Link → Zoom Meeting) on Buzz Event.buzz_event.py—create_meeting_on_zoom()+update_zoom_meeting(), mirroring the webinar methods;on_updatenow syncs both.event_ticket.py—create_zoom_registration_if_applicable()branches: creates a registration withmeetingset when the event has a meeting.api/__init__.py— ticket details returnszoom_meetingalongsidezoom_webinar.Note on laziness
The ticket's existing
zoom_webinar_registrationlink points at the now-generic registration doctype, so it holds meeting registrations too — no new ticket field, and the join-URL read needed only a one-field extension.Open (not in this PR)
UX for choosing Meeting vs Webinar on the event — both
create_*_on_zoommethods are whitelisted; wiring a desk button / dashboard toggle is a follow-up.Tests
All mocked — no real Zoom calls.
47 passing (buzz_event, incl. 2 new) · 7 passing (event_ticket, incl. 1 new). ruff clean.
🤖 Generated with Claude Code