Skip to content

Conversation

@jmesnil
Copy link
Collaborator

@jmesnil jmesnil commented Dec 10, 2025

This fixes #522.

This fixes a2aproject#522.

Signed-off-by: Jeff Mesnil <jmesnil@ibm.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jmesnil, 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 significantly refactors the internal handling of JSON-RPC requests by centralizing validation logic. The change aims to improve code maintainability and consistency by moving common validation checks from individual request classes into a shared base method. This streamlines the creation of new JSON-RPC request types and ensures uniform adherence to protocol specifications, ultimately making the codebase more robust and easier to extend.

Highlights

  • Centralized JSON-RPC Request Validation: Introduced a new protected method validateAndSetJsonParameters in the base JSONRPCRequest class to centralize common validation logic for JSON-RPC version, method name, ID type, and parameter presence. This eliminates redundant validation code across various request implementations.
  • Simplified Request Constructors and Builders: Refactored constructors and builders in all concrete JSONRPCRequest subclasses (e.g., CancelTaskRequest, GetTaskRequest, SendMessageRequest) to leverage the new centralized validation. The explicit method parameter has been removed from these constructors and builders, as the method name is now implicitly handled by the base class.
  • Deprecated Method Setters: The method setter in the Builder classes for various JSON-RPC requests has been deprecated, reinforcing that the method name is now an intrinsic property of the request type rather than a configurable parameter.
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.

@jmesnil jmesnil requested a review from ehsavoie December 10, 2025 16:21
Copy link
Contributor

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

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 is a great refactoring effort to centralize the validation logic for JSON-RPC request classes. By moving the validation to a shared method in the JSONRPCRequest superclass, you've successfully removed a significant amount of duplicated code, making the request classes cleaner and more maintainable. The changes are consistently applied across all relevant classes. I've found one potential regression where the behavior of a constructor has changed, which I've detailed in a specific comment. Overall, this is a solid improvement to the codebase.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Jeff Mesnil <jmesnil@ibm.com>
@ehsavoie ehsavoie merged commit ce36bdd into a2aproject:main Dec 11, 2025
10 checks passed
@jmesnil jmesnil added this to the 1.0.0 milestone Dec 11, 2025
kabir pushed a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
…ject#530)

This fixes a2aproject#522.

---------

Signed-off-by: Jeff Mesnil <jmesnil@ibm.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Consolidate validation of JSON-RPC requests

2 participants