-
Notifications
You must be signed in to change notification settings - Fork 146
Code generation: update services and models #1536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fbac9c4 to
db112ac
Compare
There was a problem hiding this 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 @AdyenAutomationBot, 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 is an automated update to the client SDK, generated from an updated OpenAPI specification. My review indicates that the changes are purely cosmetic, involving reordering of import statements, minor formatting adjustments, and slight rephrasing of Javadoc comments across numerous files. There are no functional changes to the codebase.
Highlights
- Automated Code Generation Update: This pull request is a result of automated code generation, updating various services and models across
acswebhooksandbalanceplatformmodules. - Formatting and Import Reordering: The changes primarily involve reordering of import statements and minor formatting adjustments (e.g., indentation, newlines) within the Java source files.
- Javadoc Comment Refinements: Javadoc comments for numerous classes, enums, and properties have been slightly rephrased or adjusted for clarity and consistency, without altering their meaning.
- No Functional Changes: Crucially, there are no functional code changes, new features, bug fixes, or modifications to existing logic introduced in this pull request. It is purely a cosmetic and structural update based on the OpenAPI specification.
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 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 or fill out our survey 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
-
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. ↩
There was a problem hiding this 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 appears to be an auto-generated update of services and models. The changes are mostly stylistic, including indentation, import order, and Javadoc formatting. I've identified a systematic issue with malformed Javadoc comments for fromJson and toJson methods across numerous model classes, which could affect documentation generation. I've added comments with suggestions to fix these.
OpenAPI spec files or templates have been modified on 08-08-2025 by commit.
Configuration Webhooks
ScoreNotificationwebhook