[checkout] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the checkout 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 delivers an automated update to the checkout service, incorporating the latest changes from the adyen-openapi specification. The modifications are largely structural, focusing on maintaining consistency in code generation, updating model definitions, and refining documentation. This ensures the client library remains current and aligned with the evolving API, facilitating smoother integration and development.

Highlights

• Automated Code Generation: This pull request is an automated update generated by the OpenAPI Generator, ensuring our checkout service models and services are synchronized with the latest API specification.
• Model Updates and Reformatting: The changes primarily involve reordering import statements, reformatting Javadoc comments, and minor code style adjustments across numerous model files. This improves code consistency and readability.
• API Deprecation Notes: Several files, such as AdditionalData3DSecure and AfterpayDetails, include updated deprecation notes in their Javadoc, guiding developers towards current best practices and alternative API fields.

🧠 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 extensive formatting changes across numerous Java model files, including reordering imports, adding blank lines, and reformatting Javadoc comments. Key changes involve consolidating multi-line equals, hashCode, and toString methods into single, excessively long lines, which the reviewer notes significantly reduces readability and maintainability. New functionality has also been added to handle explicit null values during JSON serialization and deserialization, including isSet boolean fields for each property and getExplicitNulls() methods. The review comments consistently highlight concerns about the decreased readability due to the single-line formatting of core methods and minor inconsistencies in Javadoc spacing.