forked from jitsi/jitsi-meet
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(breakout-rooms, persistent-lobby): support for using both these m…
…odules together
- Loading branch information
Showing
3 changed files
with
75 additions
and
5 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
-- Handle room destroy requests it such a way that it can be suppressed by other | ||
-- modules that handle room lifecycle and wish to keep the room alive. | ||
|
||
function handle_room_destroy(event) | ||
local room = event.room; | ||
local reason = event.reason; | ||
local caller = event.caller; | ||
|
||
module:log('info', 'Destroying room %s (requested by %s)', room.jid, caller); | ||
room:set_persistent(false); | ||
room:destroy(nil, reason); | ||
end | ||
|
||
module:hook_global("maybe-destroy-room", handle_room_destroy, -1); | ||
module:log('info', 'loaded'); |