Convert hook context models to dataclasses

[JohnRichard4096]

Sourcery 总结

将 hook 上下文模型从 Pydantic BaseModel 转换为 Python dataclasses

改进点:

• 将 TransactionContext 和 TransactionComplete 类替换为 @DataClass 实现
• 将字段定义从 pydantic Field 切换到 dataclasses.field 并更新导入

Original summary in English

Summary by Sourcery

Convert hook context models from Pydantic BaseModel to Python dataclasses

Enhancements:

• Replace TransactionContext and TransactionComplete classes with @DataClass implementations
• Switch field definitions from pydantic Field to dataclasses.field and update imports

[sourcery-ai]

审阅者指南 (在小型PR上折叠)

审阅者指南

此PR通过将 pydantic 的 BaseModel 和 Field 用法替换为 Python 内置的 dataclasses，重构了 TransactionContext 和 TransactionComplete 模型，并相应地更新了导入、装饰器和字段定义。

重构后的 TransactionContext 和 TransactionComplete 数据类类图

classDiagram
    class TransactionContext {
        +str user_id
        +str currency
        +float amount
        +str action_type
        +cancel(reason: str = "")
        +commit_update()
    }
    class TransactionComplete {
        +str message
        +float source_balance
        +float new_balance
        +float timestamp
        +str user_id
    }

Loading

文件级别变更

变更	详情	文件
将 pydantic BaseModel 继承替换为 dataclass	将 BaseModel 导入替换为 dataclass 装饰器和 field 导入 为两个模型类添加了 @DataClass 装饰器 从 TransactionContext 和 TransactionComplete 中移除了 BaseModel 子类化	nonebot_plugin_value/hook/context.py
将 pydantic Field 定义替换为 dataclasses.field	将所有类属性上的 Field(...) 替换为 field(...)	nonebot_plugin_value/hook/context.py

---

提示与命令

与 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 来触发新审查！

自定义您的体验

访问您的 仪表板 以：

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

获取帮助

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

Original review guide in English

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refactors the TransactionContext and TransactionComplete models by replacing pydantic BaseModel and Field usage with Python’s built-in dataclasses, updating imports, decorators, and field definitions accordingly.

Class diagram for refactored TransactionContext and TransactionComplete dataclasses

classDiagram
    class TransactionContext {
        +str user_id
        +str currency
        +float amount
        +str action_type
        +cancel(reason: str = "")
        +commit_update()
    }
    class TransactionComplete {
        +str message
        +float source_balance
        +float new_balance
        +float timestamp
        +str user_id
    }

Loading

File-Level Changes

Change	Details	Files
Replaced pydantic BaseModel inheritance with dataclass	Swapped BaseModel import for dataclass decorator and field import Added @DataClass decorator to both model classes Removed BaseModel subclassing from TransactionContext and TransactionComplete	nonebot_plugin_value/hook/context.py
Replaced pydantic Field definitions with dataclasses.field	Replaced Field(...) with field(...) on all class attributes	nonebot_plugin_value/hook/context.py

---

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!

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.

[JohnRichard4096]

@sourcery-ai title

[sourcery-ai]

你好 - 我已经审阅了你的更改 - 这里有一些反馈：

• 更新类文档字符串，移除对 Pydantic BaseModel 的引用，因为这些类现在是纯粹的 dataclasses。
• 确保所有依赖于 Pydantic 特定方法（如 .dict()、.json() 或字段验证）的现有逻辑都已重构，以便与 dataclasses 正确协作。
• 如果你仍然需要验证或序列化功能，可以考虑实现 post_init 钩子或实用函数来模拟已移除的 Pydantic 行为。

AI 代理的提示

请处理此代码审查中的评论：

## 总体评论
- 更新类文档字符串，移除对 Pydantic BaseModel 的引用，因为这些类现在是纯粹的 dataclasses。
- 确保所有依赖于 Pydantic 特定方法（如 .dict()、.json() 或字段验证）的现有逻辑都已重构，以便与 dataclasses 正确协作。
- 如果你仍然需要验证或序列化功能，可以考虑实现 __post_init__ 钩子或实用函数来模拟已移除的 Pydantic 行为。

---

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

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我更有用！请点击每个评论上的 👍 或 👎，我将使用这些反馈来改进你的评论。}

Original comment in English

Hey there - I've reviewed your changes - here's some feedback:

• Update the class docstrings to remove references to Pydantic BaseModel now that these classes are pure dataclasses.
• Ensure all existing logic depending on Pydantic-specific methods (like .dict(), .json(), or field validation) is refactored to work correctly with dataclasses.
• If you still require validation or serialization features, consider implementing post_init hooks or utility functions to emulate the dropped Pydantic behaviors.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Update the class docstrings to remove references to Pydantic BaseModel now that these classes are pure dataclasses.
- Ensure all existing logic depending on Pydantic-specific methods (like .dict(), .json(), or field validation) is refactored to work correctly with dataclasses.
- If you still require validation or serialization features, consider implementing __post_init__ hooks or utility functions to emulate the dropped Pydantic behaviors.

---

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

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}