Skip to content

Conversation

@fjuma
Copy link
Collaborator

@fjuma fjuma commented Jul 18, 2025

Description

  • 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)

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.

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 addresses a bug in the JSONRPCVoidResponseSerializer's constructor. The change ensures that the serializer is properly initialized with the correct generic type information, which is essential for Jackson to correctly handle JSONRPCResponse<Void> objects during serialization, ultimately improving the robustness and correctness of JSON-RPC void response handling.

Highlights

  • Constructor Initialization Fix: The JSONRPCVoidResponseSerializer's no-argument constructor has been updated to correctly initialize its StdSerializer superclass. It now explicitly constructs the JSONRPCResponse<Void> parametric type using TypeFactory.defaultInstance().constructParametricType(), ensuring proper type handling by Jackson.
  • Code Simplification: An unnecessary constructor, JSONRPCVoidResponseSerializer(Class<JSONRPCResponse<Void>> vc), has been removed. This simplifies the class's initialization logic and removes a potentially redundant entry point.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

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 fixes the constructor for JSONRPCVoidResponseSerializer to properly handle the generic type JSONRPCResponse<Void> during Jackson serialization. I've added one medium severity comment regarding line length to improve code style and readability.


public JSONRPCVoidResponseSerializer(Class<JSONRPCResponse<Void>> vc) {
super(vc);
super(TypeFactory.defaultInstance().constructParametricType(JSONRPCResponse.class, Void.class));
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This line exceeds the common 100-character line length limit, which can impact readability. To maintain a consistent code style, I recommend wrapping the line.

super(TypeFactory.defaultInstance().constructParametricType(
        JSONRPCResponse.class, Void.class));

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

@fjuma fjuma merged commit da6e49d into a2aproject:main Jul 18, 2025
3 checks passed
kabir pushed a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
# Description

- [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)
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.

2 participants