-
Notifications
You must be signed in to change notification settings - Fork 36
[ManagementAPIs] Code generation: update services and models #455
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
base: main
Are you sure you want to change the base?
Conversation
e247482
to
bdee263
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 contains automatically generated code updates for the Adyen Management APIs and Balance Control API. The changes primarily involve refactoring the underlying API client logic for improved error handling and request sending, along with minor stylistic formatting adjustments and documentation updates across various service and model files.
Highlights
- API Client Refactoring: The core logic for sending API requests and handling HTTP responses has been centralized within the
common.SendAPIRequest
function. This eliminates redundant error handling and JSON unmarshalling code from individual API service files, leading to cleaner and more maintainable code. - Code Formatting & Readability: Various Go files have received minor stylistic updates, including changes to import statement formatting, multiline curly braces for return statements, and single-line array declarations for enum values. These changes improve overall code consistency and readability.
- Documentation Updates: Minor textual adjustments and formatting improvements have been applied to inline comments and API documentation strings across several service files, enhancing clarity for developers.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 or fill out our survey to provide feedback.
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 appears to be from an automated code generation process, introducing mostly formatting changes and updates to services and models. However, there are a few critical issues that need to be addressed. Several files have had necessary imports like encoding/json
and io/ioutil
removed, which will cause compilation errors. Additionally, io/ioutil
is deprecated and should be replaced with io
. There is also significant code duplication in error handling across many of the API methods, which should be refactored. Finally, there are some minor formatting inconsistencies that should be addressed in the code generator.
12bd805
to
3d75fe1
Compare
5a0bd89
to
72cad91
Compare
0fbe6d2
to
2b622d0
Compare
2ba5f9c
to
caaae11
Compare
4f7f0c2
to
a0103f4
Compare
100e224
to
8148ca6
Compare
44a1532
to
1292203
Compare
OpenAPI spec files or templates have been modified on 03-10-2025 by commit.