-
Notifications
You must be signed in to change notification settings - Fork 36
[PaymentsAPIs] Code generation: update services and models #456
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
476c10f
to
5a4decc
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 primarily updates the Payments APIs by regenerating code based on the latest OpenAPI specifications. The changes encompass various Go files within the binlookup
, checkout
, and disputes
modules. Key updates include adding new API endpoints and models, enhancing data structures for payment modification requests, and refining existing documentation. These changes ensure the API client remains synchronized with the latest API definitions, supporting new features and improving data handling capabilities.
Highlights
- API Service Updates: Updated API service files across
binlookup
,checkout
, anddisputes
to include thestrings
package import, indicating potential new string manipulation functionalities in API calls. - Enhanced Data Capture for Modifications: Introduced new models for enhanced data capture in modification requests, including
EnhancedSchemeData
forPaymentAmountUpdateRequest
,PaymentCancelRequest
,PaymentRefundRequest
, andPaymentReversalRequest
, andStandalonePaymentCancelRequest
. - New Shopper Validation Feature: Added a new
ValidateShopperId
endpoint and associated models (ValidateShopperIdRequest
,ValidateShopperIdResponse
,ShopperIdPaymentMethod
,Result
,InvalidField
) under thecheckout
API, suggesting new shopper validation capabilities. - New Payment Method Support: Introduced new UPI payment method models (
UPIPaymentMethod
,UPIPaymentMethodAllOf
) and updated thecheckout/model_payment_details.go
to include 'payme' and 'payme_pos' as allowed payment method types. - Documentation and Clarity Improvements: Refined docstrings and comments across numerous files, including updates to
pspReference
links, deprecation notices for fields likeauthenticationOnly
andrecurringDetailReference
, and improved clarity for various parameters. - Data Model Enhancements: Adjusted the
maxLength
forAirlineLegFareBaseCode
inmodel_additional_data_airline.go
from 6 to 15 characters, allowing for more detailed fare basis codes.
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 an automated update based on changes to the OpenAPI specification. The changes include adding new models and endpoints, updating existing models with new fields and documentation, and various formatting adjustments across a large number of files. The generated code seems correct and consistent with the described changes. I've pointed out a couple of recurring formatting inconsistencies that deviate from standard Go style, which could be addressed in the code generator for future updates.
ff378ad
to
5268cea
Compare
a00f81b
to
203fa8b
Compare
b5fc206
to
5e08423
Compare
292879a
to
63aafcc
Compare
d0a656b
to
df7fe62
Compare
OpenAPI spec files or templates have been modified on 16-09-2025 by commit.