add message level and content level opaque_body

[BeautyyuYanli]

This is part of langgenius/dify-official-plugins#2492

[gemini-code-assist]

Summary of Changes

Hello @BeautyyuYanli, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new opaque_body field to message content and assistant message models, enabling the attachment of arbitrary JSON data. This enhancement provides a flexible way to store additional, unstructured information at both the message content and message levels, improving extensibility without altering core message structures.

Highlights

• Introduction of opaque_body fields: New opaque_body: JsonValue | None = None fields have been added to both PromptMessageContent and AssistantPromptMessage models, allowing for flexible storage of arbitrary JSON data.
• Pydantic JsonValue type integration: The JsonValue type from Pydantic is now imported and utilized for the new opaque_body fields, ensuring proper type hinting and validation for JSON data.
• Future annotations import: The from __future__ import annotations import has been added to message.py to enable postponed evaluation of type annotations, improving forward compatibility and reducing circular import issues.
• New test case for opaque_body: A new test, test_assistant_message_opaque_body_roundtrip, has been added to test_llm_result.py to verify the correct handling and round-tripping of opaque_body data at both message and content levels.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request successfully introduces opaque_body fields to PromptMessageContent and AssistantPromptMessage models, allowing for flexible storage of arbitrary JSON data at both the content and message levels. The addition of JsonValue from Pydantic is appropriate for this purpose. The new test case test_assistant_message_opaque_body_roundtrip effectively verifies the functionality of these new fields, ensuring that the opaque_body can be correctly set and retrieved. The changes are well-implemented and align with the stated goal of the pull request.