From f6bf8be94d036336656f696f2ecfd43834e67770 Mon Sep 17 00:00:00 2001 From: Luna Date: Sun, 21 Apr 2019 23:17:39 -0300 Subject: [PATCH] admin_api.guilds: use GUILD_DELETE instead of GUILD_UPDATE --- litecord/blueprints/admin_api/guilds.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/litecord/blueprints/admin_api/guilds.py b/litecord/blueprints/admin_api/guilds.py index 1de09b2..711ea26 100644 --- a/litecord/blueprints/admin_api/guilds.py +++ b/litecord/blueprints/admin_api/guilds.py @@ -51,16 +51,15 @@ async def update_guild(guild_id: int): # j.unavailable is there app.guild_store.set(guild_id, 'unavailable', j['unavailable']) - # if this was unavailable but now its not, we must dispatch a - # GUILD_CREATE to the subscribers, not GUILD_UPDATE. GUILD_UPDATE - # is used on the reverse scenario. guild = await app.storage.get_guild(guild_id) # TODO: maybe we can just check guild['unavailable']...? if old_unavailable and not new_unavailable: + # guild became available await app.dispatcher.dispatch_guild(guild_id, 'GUILD_CREATE', guild) else: - await app.dispatcher.dispatch_guild(guild_id, 'GUILD_UPDATE', guild) + # guild became unavailable + await app.dispatcher.dispatch_guild(guild_id, 'GUILD_DELETE', guild) return jsonify(guild)