[transfers] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the transfers service.

The commit history of this PR reflects the adyen-openapi commits that have been applied.

[gemini-code-assist]

Summary of Changes

Hello @AdyenAutomationBot, I'm Gemini Code Assist¹! 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 contains automated updates to the generated Java models and services for the transfers API. These changes primarily focus on code formatting, import organization, and minor structural adjustments within the model classes, ensuring consistency with the latest OpenAPI specification.

Highlights

• Code Formatting and Readability: Standardized whitespace, line breaks, and Javadoc comments across numerous model classes for improved code consistency.
• Serialization Logic Updates: Refinements to equals, hashCode, toString, fromJson, and toJson methods in generated models, including better handling of isSet flags for JSON serialization.
• Import Optimization: Imports have been reordered and optimized in many files, including the core JSON.java utility class.
• OpenAPI Generator Alignment: Updates to enum constructors and annotations (@JsonValue, @JsonCreator) to align with the latest OpenAPI Generator output for robust serialization/deserialization.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

[gemini-code-assist]

Code Review

This pull request introduces a number of changes to the generated models, primarily related to formatting and code style. While most of these are minor, I've identified a few patterns that could be improved for better code quality and maintainability. My comments focus on these patterns, which seem to originate from the generator templates. Specifically, I've noted unnecessary trailing semicolons in equals methods, single-line hashCode methods for classes with many fields which harms readability, and significant code duplication in the oneOf deserialization logic. Addressing these in the generator templates would improve the quality of the generated code across the board.