自上一个问题以来,我一直在尝试使其正常工作,但是当我成功地通过更新的profile
获取过去的简历后,尝试执行setBio
命令时,现在会出现错误命令:
bio[message.author.id].join is not a function
我已经开始意识到这个问题,但是我不知道如何正确解决它。
以下是发生错误的代码:
case 'setBio':
if(!bio[message.author.id]) {
let messages = message.channel.messages;
let authorMessages = messages.filter(m => m.author.id === message.author.id);
let setBioCommands = authorMessages.filter(m => m.content.startsWith('!setBio'));
let firstBio = setBioCommands.last();
message.channel.send('I found a Bio you have previously set. Do you want to confirm the change to that Bio?').then(r => r.delete(10000));
message.react('✅').then(() => message.react('❎'));
const filter = (reaction, user) => {
return ['✅', '❎'].includes(reaction.emoji.name) && user.id === message.author.id;
};
message.awaitReactions(filter, { max: 1, time: 10000, errors: ['time'] })
.then(collected => {
const reaction = collected.first();
if (reaction.emoji.name === '✅') {
bio[message.author.id] = firstBio
message.reply('Past Bio successfully restored!')
.then(msg => msg.delete(3000));
}
else {
message.reply('Okey, I\'ll delete this Bio.')
.then(msg => msg.delete(3000));
}
})
.catch(collected => {
message.channel.send('You didn\'t respond, so I\'ll throw this Bio into the abyss. *Buh-bye!*');
});
} else {
let newArr = args.slice(1)
bio[message.author.id] = newArr
message.channel.send('Your bio has been changed!')
.then(msg => msg.delete(3000));
}
break;
case 'profile':
if(!bio[message.author.id]) {
return message.channel.send('Sorry, please set a bio with `!setBio` to view your profile!')
.then(msg => msg.delete(3000));
} else {
const embed = new Discord.RichEmbed()
.setTitle('__' + message.author.username + '\'s Profile__')
.addField(`Bio:`, bio[message.author.id].join(" ")) /// this is where the error is
.setColor(message.member.colorRole.color)
.setThumbnail(message.author.avatarURL)
message.channel.send(embed);
}
break;
答案 0 :(得分:1)
该错误告诉您bio[message.author.id]
没有.join()
方法。 .join()
通常用于具有这种方法的数组。您可能期望bio[message.author.id]
是一个数组,但是它可能是其他某个对象。
尝试登录bio[message.author.id]
,以更好地了解后台发生的情况(调试过程),然后从那里进行操作。