Skip to content

Conversation

@kabir
Copy link
Collaborator

@kabir kabir commented Dec 15, 2025

Fixes #498 🦕

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kabir, 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 refactors the API for creating builder instances across various classes by replacing direct constructor calls with static factory methods. This change enhances the API's usability and adheres to modern Java best practices, making the code more idiomatic and maintainable. The update also includes minor API cleanups like renaming a method and removing a deprecated one, ensuring a more streamlined and consistent developer experience.

Highlights

  • API Consistency: Replaced direct instantiation of Builder constructors (e.g., new MyClass.Builder()) with static factory methods (e.g., MyClass.builder()) across the codebase. This change aligns with common Java API design patterns, improving readability and consistency.
  • Builder Access Modifiers: Modified the constructors of internal Builder classes to be private, enforcing the use of the new static factory methods for creating builder instances.
  • Builder Overloads: Introduced overloaded static factory methods for builders that support copying existing instances (e.g., MyClass.builder(existingInstance)), providing a clearer and more idiomatic way to create builders from existing objects.
  • API Renaming: Renamed the authenticationInfo method to authentication within PushNotificationConfig.Builder for better clarity and consistency. Additionally, the deprecated additionalInterfaces method in AgentCard.Builder was removed in favor of supportedInterfaces.
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.

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 consistently replaces public builder constructors with static factory methods across the codebase, which is a great improvement for API consistency and control over object creation. The changes are extensive and well-executed. I've found a couple of minor issues to address.

.tags(Collections.singletonList("hello world"))
.examples(List.of("hi", "hello world"))
.build()))
.protocolVersion("0.3.0")
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe this should be updated to 1.0.0

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'll do that in another PR coming soon

@kabir kabir merged commit a2499fb into a2aproject:main Dec 16, 2025
11 checks passed
kabir added a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
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.

[Feat]: Standardize on builder() method for a2a API

2 participants