Skip to content

Conversation

@AdyenAutomationBot
Copy link
Collaborator

@AdyenAutomationBot AdyenAutomationBot commented Sep 23, 2025

Management API

  • Add enum value BR_SCHEMES in PaymentMethodResponse and PaymentMethodSetupInfo

Management Webhooks

  • In TerminalAssignmentNotificationRequest add attribute assignedToStoreId
  • Add enum value dataReview in VerificationError and VerificationErrorRecursive

Classic Payments

  • In Recurring add enum values EXTERNAL and ONECLICK_RECURRING

OpenAPI spec files or templates have been modified on 24-09-2025 by commit.

@AdyenAutomationBot AdyenAutomationBot requested a review from a team as a code owner September 23, 2025 11:18
@gemini-code-assist
Copy link
Contributor

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 synchronizes the client library with the latest OpenAPI specification for Adyen's services and models. The update is automated and primarily focuses on maintaining code quality through reordering imports, adding blank lines, and refining Javadoc comments across a wide range of generated Java classes.

Highlights

  • Automated Code Generation Update: This pull request contains updated services and models generated from the latest OpenAPI specification files or templates, as indicated by the commit from September 23, 2025.
  • Code Formatting and Readability: Numerous Java files across acswebhooks, balancecontrol, and balanceplatform packages have undergone reordering of import statements, addition of blank lines for better separation, and minor adjustments to Javadoc comments. These changes enhance code consistency and readability.
  • Minor Javadoc Adjustments: Several Javadoc comments have been reformatted, particularly for enum descriptions and parameter explanations, to improve clarity and adherence to style guidelines.
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

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 appears to be a large-scale, auto-generated update to models and services, primarily focused on code formatting and style. While many of the changes, such as standardizing indentation to 4 spaces, are positive, some of the new formatting conventions have reduced code readability in key areas. Specifically, the equals() and hashCode() methods in many of the updated model classes have become long, single-line statements that are difficult to read and maintain. I've added a couple of specific comments on one of the files to illustrate this, and I recommend applying similar fixes to all other affected files to improve maintainability.

@AdyenAutomationBot AdyenAutomationBot force-pushed the sdk-automation/models branch 5 times, most recently from 299e4d5 to 91eb261 Compare September 24, 2025 20:09
@gcatanese gcatanese merged commit fdd0267 into main Sep 25, 2025
5 checks passed
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.

3 participants