Skip to content

optimize: Improved JSONRPCErrorDeserializer - #136

Merged
kabir merged 1 commit into
a2aproject:mainfrom
sunyuhan1998:fix-issue-23
Jul 2, 2025
Merged

kabir merged 1 commit into
a2aproject:mainfrom
sunyuhan1998:fix-issue-23

Conversation

@sunyuhan1998

Copy link
Copy Markdown
Contributor

This PR includes the following changes:

  1. Improved the JSONRPCErrorDeserializer so that it can return the correct subclass based on the error code, instead of always returning JSONRPCError.

  2. Added corresponding unit tests.

Fixes #23

…so that it can return the correct subclass based on the error code, instead of always returning `JSONRPCError`. 2. Added corresponding unit tests.

Signed-off-by: Sun Yuhan <[email protected]>

@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.

Summary of Changes

Hello @sunyuhan1998, 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 enhances the error handling mechanism by ensuring that JSONRPC errors are correctly deserialized into their specific subclasses, providing more accurate error information. This is achieved by mapping error codes to their corresponding classes within the deserializer and adding corresponding unit tests.

Highlights

  • JSONRPCError Deserialization: The JSONRPCErrorDeserializer is improved to return the correct subclass of JSONRPCError based on the error code, instead of always returning a generic JSONRPCError.
  • Default Error Codes: Each JSONRPCError subclass now has a DEFAULT_CODE constant, making it easier to identify and manage error types.
  • Unit Tests: Added unit tests to verify that the deserializer returns the correct JSONRPCError subclass for various error codes.
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. ↩

@sunyuhan1998 sunyuhan1998 changed the title optimize: Improved JSONRPCErrorDeserializer optimize: Improved JSONRPCErrorDeserializer Jun 27, 2025

@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 enhances the JSONRPCErrorDeserializer to correctly deserialize JSONRPC errors into their specific subclasses based on the error code. It also introduces corresponding unit tests to verify the deserialization logic. The error classes now have a DEFAULT_CODE constant.

@sunyuhan1998

Copy link
Copy Markdown
Contributor Author

Hi @kabir @fjuma @maeste ,Can you help review this PR ? Thank you very much!

@kabir
kabir merged commit e97df4c into a2aproject:main Jul 2, 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.

Look into deserialization for classes that extend JSONRPCError

2 participants