✨ 适配新增的 "server_version" 和 "server_type" 字段

[17TheWord]

Sourcery 总结

增强:

• 调整 getMessage 函数，使其能够处理消息对象中新增的 server_version、server_type 和 event_name 字段

Original summary in English

Summary by Sourcery

Enhancements:

• Adapt the getMessage function to handle the new server_version, server_type, and event_name fields in the message object

[sourcery-ai]

## Sourcery 评审员指南

此拉取请求调整了 `getMessage` 函数，以适应消息有效负载中新添加的 `server_version` 和 `server_type` 字段。 还添加了 `event_name` 参数。

#### 处理消息的顺序图

```mermaid
sequenceDiagram
  participant Config
  participant SendMsg
  participant getMessage

  Config->>SendMsg: getConfig()
  SendMsg->>getMessage: getMessage(jsonMsg, mc_qq_display_server_name)
  activate getMessage
  getMessage-->>SendMsg: msg
  deactivate getMessage
  SendMsg->>SendMsg: serverConfig = mc_qq_server_list.find(...)
  SendMsg->>SendMsg: msg = msg.replace(...)

消息对象的更新类图

Loading

classDiagram
  class Message {
    server_name: string
    server_version: string
    server_type: string
    event_name: string
    post_type: string
    player: string
    message: string
    sub_type: string
  }
  note for Message "Added server_version, server_type and event_name fields"

文件级别更改

变更	详情	文件
调整 getMessage 函数以处理消息有效负载中的新 server_version 和 server_type 字段。	修改了 getMessage 函数以接受解构参数中的 server_version 和 server_type。 event_name 参数也被添加到解构参数中。	components/SendMsg.js

---

提示和命令

与 Sourcery 交互

• 触发新的审查： 在拉取请求上评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审查评论。
• 从审查评论生成 GitHub issue： 通过回复审查评论，要求 Sourcery 从审查评论创建一个 issue。 您还可以回复带有 @sourcery-ai issue 的审查评论以从中创建一个 issue。
• 生成拉取请求标题： 在拉取请求标题中的任何位置写入 @sourcery-ai 以随时生成标题。 您也可以在拉取请求上评论 @sourcery-ai title 以随时（重新）生成标题。
• 生成拉取请求摘要： 在拉取请求正文中的任何位置写入 @sourcery-ai summary 以随时在您想要的位置生成 PR 摘要。 您也可以在拉取请求上评论 @sourcery-ai summary 以随时（重新）生成摘要。
• 生成评审员指南： 在拉取请求上评论 @sourcery-ai guide 以随时（重新）生成评审员指南。
• 解决所有 Sourcery 评论： 在拉取请求上评论 @sourcery-ai resolve 以解决所有 Sourcery 评论。 如果您已经解决了所有评论并且不想再看到它们，这将非常有用。
• 驳回所有 Sourcery 审查： 在拉取请求上评论 @sourcery-ai dismiss 以驳回所有现有的 Sourcery 审查。 如果您想重新开始新的审查，这将特别有用 - 不要忘记评论 @sourcery-ai review 以触发新的审查！
• 为 issue 生成行动计划： 在 issue 上评论 @sourcery-ai plan 以为其生成行动计划。

自定义您的体验

访问您的 仪表板 以：

• 启用或禁用审查功能，例如 Sourcery 生成的拉取请求摘要、评审员指南等。
• 更改审查语言。
• 添加、删除或编辑自定义审查说明。
• 调整其他审查设置。

获得帮助

• 联系我们的支持团队 提出问题或反馈。
• 访问我们的 文档 以获取详细的指南和信息。
• 通过在 X/Twitter、LinkedIn 或 GitHub 上关注我们，与 Sourcery 团队保持联系。

```

Original review guide in English

Reviewer's Guide by Sourcery

This pull request adapts the getMessage function to accommodate the newly added server_version and server_type fields in the message payload. The event_name parameter was also added.

Sequence diagram for processing a message

Loading

sequenceDiagram
  participant Config
  participant SendMsg
  participant getMessage

  Config->>SendMsg: getConfig()
  SendMsg->>getMessage: getMessage(jsonMsg, mc_qq_display_server_name)
  activate getMessage
  getMessage-->>SendMsg: msg
  deactivate getMessage
  SendMsg->>SendMsg: serverConfig = mc_qq_server_list.find(...)
  SendMsg->>SendMsg: msg = msg.replace(...)

Updated class diagram for the message object

Loading

classDiagram
  class Message {
    server_name: string
    server_version: string
    server_type: string
    event_name: string
    post_type: string
    player: string
    message: string
    sub_type: string
  }
  note for Message "Added server_version, server_type and event_name fields"

File-Level Changes

Change	Details	Files
Adapt the getMessage function to handle new server_version and server_type fields in the message payload.	Modified the getMessage function to accept server_version and server_type in the destructured parameters. The event_name parameter was also added to the destructured parameters.	components/SendMsg.js

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

嘿 @17TheWord - 我已经查看了你的更改 - 这里有一些反馈：

总体评论：

• 考虑将 Config.getConfig() 解构为单独的变量，以提高可读性。

以下是我在审查期间查看的内容

• 🟢 一般问题：一切看起来都很好
• 🟢 安全性：一切看起来都很好
• 🟢 测试：一切看起来都很好
• 🟢 复杂性：一切看起来都很好
• 🟢 文档：一切看起来都很好

---

Sourcery 对于开源是免费的 - 如果你喜欢我们的评论，请考虑分享它们 ✨

• X
• Mastodon
• LinkedIn
• Facebook

<sub>帮助我变得更有用！请点击每个评论上的 👍 或 👎，我将使用反馈来改进你的评论。</sub>

Original comment in English

Hey @17TheWord - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider destructuring Config.getConfig() into individual variables to improve readability.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

<sub>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.</sub>