Skip to content

Conversation

@AdyenAutomationBot
Copy link
Collaborator

This PR contains the automated changes for the relayedauthorizationwebhooks 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 January 16, 2026 12:53
@gemini-code-assist
Copy link
Contributor

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 integrates a significant update to the relayedauthorizationwebhooks service by introducing a complete set of new TypeScript models and a dedicated webhook handler. This automated update ensures that the client library is fully aligned with the latest API definitions, providing developers with accurate and up-to-date data structures for handling relayed authorization events and streamlining integration efforts.

Highlights

  • New Models for Relayed Authorization Webhooks: A comprehensive suite of new TypeScript models has been added to support the relayedauthorizationwebhooks service. These models define various data structures for amounts, authentication, authorization decisions, balance mutations, bank account details, addresses, cards, card configurations, delivery contacts, merchant data, payment instruments, 3D Secure, transaction rules, and validation results.
  • Webhook Event Handler: A new RelayedAuthorizationWebhooksHandler class has been introduced to facilitate the deserialization and generic handling of relayedauthorizationwebhooks events, ensuring proper type recognition and processing of incoming webhook payloads.
  • Automated Code Generation: All changes in this pull request are a result of automated code generation, ensuring the client library remains synchronized with the latest adyen-openapi specifications for the relayedauthorizationwebhooks service.

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

Copy link
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 PR introduces auto-generated TypeScript models and a handler for the relayedauthorizationwebhooks service. The generated code is comprehensive. I've made a few suggestions to improve code quality and maintainability, such as fixing a typo in a comment, improving an error message for better debuggability, and adhering to the common convention of ending files with a newline.

export * from "./validationResult"

// serializing and deserializing typed objects
export * from "./objectSerializer" No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's a common convention and good practice to end files with a newline character. This can prevent issues with some tools, file concatenation, and version control systems.

Suggested change
export * from "./objectSerializer"
export * from "./objectSerializer"

*/
"formFactor": Card.FormFactorEnum;
/**
* Last last four digits of the card number.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

There's a minor typo here. It should probably be 'The last four digits...'.

Suggested change
* Last last four digits of the card number.
* The last four digits of the card number.

return this.getRelayedAuthorisationRequest();
}

throw new Error("Could not parse the json payload: " + this.payload);
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The error message for an unrecognized webhook type is not very helpful for debugging. Concatenating the payload object with a string will result in "[object Object]". Using JSON.stringify will provide the actual payload content in the error message, making it much easier to diagnose issues with incoming webhooks.

Suggested change
throw new Error("Could not parse the json payload: " + this.payload);
throw new Error("Could not parse the json payload: " + JSON.stringify(this.payload));

return relayedAuthorizationWebhooks.ObjectSerializer.deserialize(this.payload, "RelayedAuthorisationRequest");
}

} No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's a common convention and good practice to end files with a newline character. This can prevent issues with some tools, file concatenation, and version control systems.

Suggested change
}
}

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