Skip to content

[paymentsapp] Code generation: update services and models#1781

Closed
AdyenAutomationBot wants to merge 1 commit intomainfrom
sdk-automation/paymentsapp
Closed

[paymentsapp] Code generation: update services and models#1781
AdyenAutomationBot wants to merge 1 commit intomainfrom
sdk-automation/paymentsapp

Conversation

@AdyenAutomationBot
Copy link
Copy Markdown
Collaborator

This PR contains the automated changes for the paymentsapp service.

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

@AdyenAutomationBot AdyenAutomationBot requested review from a team as code owners March 9, 2026 13:31
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 updates the generated services and models for the paymentsapp service. The primary change involves a refactoring of the package structure for these models, moving them from com.adyen.model.paymentsapp to com.adyen.model.java. This is an automated update to align with the latest adyen-openapi specifications.

Highlights

  • Package Renaming: All generated model classes previously located in com.adyen.model.paymentsapp have been moved to the com.adyen.model.java package.
  • Automated Code Generation: This update is a result of automated code generation, reflecting recent changes in the adyen-openapi definitions.

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

Changelog
  • src/main/java/com/adyen/model/paymentsapp/AbstractOpenApiSchema.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/BoardingTokenRequest.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/BoardingTokenResponse.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/DefaultErrorResponseEntity.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/InvalidField.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/JSON.java
    • Updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/PaymentsAppDto.java
    • Renamed file and updated package declaration.
  • src/main/java/com/adyen/model/paymentsapp/PaymentsAppResponse.java
    • Renamed file and updated package declaration.
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.

Copy link
Copy Markdown
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, part of an automated code generation process, updates services and models by moving model classes from the com.adyen.model.paymentsapp package to com.adyen.model.java. While most files have been correctly renamed and moved, a critical issue was found with JSON.java. Its package declaration was changed, but the file was not moved to the new directory structure, which will cause a compilation error. I've left a specific comment on that file. It also appears that consumer classes, such as services and tests, have not been updated to reflect this package change, which will also need to be addressed.

@@ -1,4 +1,4 @@
package com.adyen.model.paymentsapp;
package com.adyen.model.java;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The package for this file has been updated to com.adyen.model.java, but the file itself has not been moved to the corresponding directory src/main/java/com/adyen/model/java/. This will cause a compilation error as the package declaration does not match the file path. This file should be moved to src/main/java/com/adyen/model/java/JSON.java to be consistent with the other model files in this PR.

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.

2 participants