Skip to content

[0.4.0] fix: Use parts instead of content for gRPC Message object#89

Merged
kabir merged 2 commits into
a2aproject:mainfrom
fjuma:grpc
Nov 10, 2025
Merged

[0.4.0] fix: Use parts instead of content for gRPC Message object#89
kabir merged 2 commits into
a2aproject:mainfrom
fjuma:grpc

Conversation

@fjuma

@fjuma fjuma commented Oct 27, 2025

Copy link
Copy Markdown
Collaborator

Description

This PR is in preparation for the 0.4.0 spec version.

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Follow the CONTRIBUTING Guide.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
    • Important Prefixes for release-please:
      • fix: which represents bug fixes, and correlates to a SemVer patch.
      • feat: represents a new feature, and correlates to a SemVer minor.
      • feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
  • Ensure the tests pass
  • Appropriate READMEs were updated (if necessary)

Fixes #88 🦕

@gemini-code-assist

gemini-code-assist Bot commented Oct 27, 2025

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @fjuma, I'm Gemini Code Assist1! 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 significant updates to the gRPC API, primarily to align with the upcoming 0.4.0 specification. The core change involves renaming the content field to parts within the Message object, alongside the addition of a new ListTasks RPC for enhanced task management. Various other API messages have been refined with clearer documentation and new fields to improve functionality and consistency, ensuring the API remains robust and developer-friendly. These changes also address and fix issue #88.

Highlights

  • gRPC Message Object Update: The Message object in the gRPC API has been updated to use a parts field instead of content for message content, aligning with the 0.4.0 spec.
  • New ListTasks RPC: A new ListTasks RPC method has been introduced, allowing for optional filtering and pagination of tasks.
  • API Field Enhancements: Several API fields across various messages (e.g., Task, Message, Artifact, PushNotificationConfig, AgentCard, AgentCapabilities, AgentSkill, TaskPushNotificationConfig) have received updated comments for clarity, specifying UUIDs for identifiers, and new fields like metadata for Part, name for FilePart, reference_task_ids for Message, icon_url for AgentCard, and state_transition_history for AgentCapabilities.
  • HTTP Path Correction: The HTTP path for CreateTaskPushNotificationConfig has been corrected from /v1/{parent=task/*/pushNotificationConfigs} to /v1/{parent=tasks/*/pushNotificationConfigs}.
  • Python gRPC Stub Regeneration: The Python gRPC stubs (a2a_pb2.py and a2a_pb2_grpc.py) have been regenerated to reflect the latest .proto definition changes.
  • Client-Side Adaptations: Client-side utilities (tck/message_utils.py and tck/transport/grpc_client.py) have been updated to correctly handle the content to parts field rename in gRPC message conversions.
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. ↩

@fjuma fjuma mentioned this pull request Oct 27, 2025
Merged
gemini-code-assist[bot]
gemini-code-assist Bot reviewed Oct 27, 2025
View reviewed changes

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the gRPC Message object to use 'parts' instead of 'content' for the 0.4.0 spec version. The changes involve modifications to the a2a.proto file, including renaming the 'content' field to 'parts' in the Message object, adding new methods, and updating descriptions. Additionally, the corresponding Python gRPC stubs are regenerated to reflect these changes. I have provided review comments to address potential issues and improve code clarity.

@kabir kabir merged commit 601bf0d into a2aproject:main Nov 10, 2025
1 check passed
unclaimed-cherry-blossom pushed a commit to unclaimed-cherry-blossom/a2a-tck that referenced this pull request Feb 11, 2026
@fjuma
[0.4.0] fix: Use parts instead of content for gRPC Message object (a2…
e793616 
…aproject#89)

# Description

This PR is in preparation for the 0.4.0 spec version.

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:

- [x] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes a2aproject#88 🦕
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kabir kabir kabir approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Bug]: Inconsistent property name between gRPC and JSON-RPC in message object

2 participants

@fjuma @kabir