Closed briantanner closed 8 years ago
Yes, as far as consistency goes this is correct, and member.unban
works only in sync code.
Though from usability standpoint I can call this behavior retarded and this will be fixed in the next version.
Initially for that case guild.ban
/unban
methods were created for use with user object or id:
const uid = user.id;
guild.ban(uid, 7).then(() => {
// user.id is no longer available in this scope
guild.unban(uid);
});
Thanks for the quick response.
I imagine this has something to do with a user being uncached after banning, but below is the code and error caused by it.