-
Notifications
You must be signed in to change notification settings - Fork 146
Code generation: update services and models #1560
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
708da7c to
bf8ffb3
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 primarily focuses on updating the client library's generated code to reflect the latest Adyen OpenAPI specifications. The changes are largely automated, ensuring the codebase remains synchronized with the API definitions. This update brings consistency in code style and expands support for various bank account identification types, contributing to a more robust and up-to-date integration.
Highlights
- Automated Code Generation Update: This pull request contains an automated update of the generated client code for Adyen services and models, ensuring synchronization with the latest OpenAPI specifications.
- Code Formatting and Standardization: Extensive reformatting and standardization of Java code have been applied across numerous model and service files, improving code consistency and readability.
- Expanded Bank Account Identification Types: The
BankAccountAccountIdentification.javafile has been updated to include new bank account identification types, aligning with expanded API capabilities.
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
-
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 updates services and models, likely from a code generator. The changes are mostly stylistic, such as re-indentation and code reformatting. However, I've noticed a recurring issue across many of the modified files: Javadoc comments for fromJson and toJson methods are malformed. They start with /** instead of /**, which can cause issues with Javadoc generation and static analysis tools. I've added comments to each affected file to point out the issue. Please ensure all Javadoc comments are correctly formatted.
73b6daf to
e52e342
Compare
3f7e2c5 to
0527d72
Compare
Checkout API
PaymentDetailsadd enumIRISUpiIntentDetailsadd attributebillingSequenceNumberPayout API
ResponseAdditionalDataSwishOpenAPI spec files or templates have been modified on 18-09-2025 by commit.