We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AT_MESSAGE_CREATE 和 MESSAGE_CREATE 事件, 推送的 Message 对象能传递完整的Member信息和User信息
AT_MESSAGE_CREATE
MESSAGE_CREATE
Message
Member
User
通过Menber.Nick和User.UserName给与用户更好的交互体验, 现在的情况是,返回的Member对象没有填充Nick字段,而是用Nick填充了User.UserName字段,导致UserName字段的意义不明确.
Menber.Nick
User.UserName
Nick
UserName
再次调用/guilds/{guild_id}/members/{user_id}接口获取完整的Member信息, 导致API的重复调用,增加服务端压力,拖慢机器人对用户的交互响应.
/guilds/{guild_id}/members/{user_id}
The text was updated successfully, but these errors were encountered:
我们统筹安排下,计划确定后这里来 update
Sorry, something went wrong.
No branches or pull requests
想要的能力是
AT_MESSAGE_CREATE
和MESSAGE_CREATE
事件,推送的
Message
对象能传递完整的Member
信息和User
信息基于想要的能力,能够实现的是
通过
Menber.Nick
和User.UserName
给与用户更好的交互体验,现在的情况是,返回的
Member
对象没有填充Nick
字段,而是用Nick
填充了User.UserName
字段,导致UserName
字段的意义不明确.如果未提供该能力,造成的影响是
再次调用
/guilds/{guild_id}/members/{user_id}
接口获取完整的Member
信息,导致API的重复调用,增加服务端压力,拖慢机器人对用户的交互响应.
The text was updated successfully, but these errors were encountered: