StyAndCo/zappyzep
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fixed mistake that made REST calls we know will fail on forcemute/unmute

Browse source
This commit is contained in:
Dark 2020-07-31 19:31:36 +02:00
parent b2957b564d
commit 532041ad0d
3 changed files with 12 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

4
backend/src/plugins/Mutes/functions/unmuteUser.ts
View file

@ -1,7 +1,7 @@
import { PluginData } from "knub";
import { MutesPluginType, UnmuteResult } from "../types";
import { CaseArgs } from "../../Cases/types";
import { resolveUser, stripObjectToScalars } from "../../../utils";
import { resolveUser, stripObjectToScalars, resolveMember } from "../../../utils";
import { memberHasMutedRole } from "./memberHasMutedRole";
import humanizeDuration from "humanize-duration";
import { CasesPlugin } from "../../Cases/CasesPlugin";
@ -16,7 +16,7 @@ export async function unmuteUser(
): Promise<UnmuteResult> {
const existingMute = await pluginData.state.mutes.findExistingMuteForUserId(userId);
const user = await resolveUser(pluginData.client, userId);
const member = await pluginData.client.getRESTGuildMember(pluginData.guild.id, userId); // Grab the fresh member so we don't have stale role info
const member = await resolveMember(pluginData.client, pluginData.guild, userId); // Grab the fresh member so we don't have stale role info
if (!existingMute && !memberHasMutedRole(pluginData, member)) return;