Skip to content

Conversation

@AdyenAutomationBot
Copy link
Collaborator

This PR contains the automated changes for the managementwebhooks 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 5, 2026 15:20
@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 delivers automated code generation updates for the managementwebhooks service. The changes are entirely cosmetic, focusing on standardizing code style, organizing imports, and refining Javadoc comments across several model and handler files. These updates ensure a cleaner, more consistent codebase without introducing any functional modifications.

Highlights

  • Code Formatting and Style: Numerous files across the managementwebhooks service have received consistent formatting updates, including the insertion of blank lines for improved readability between field and method declarations.
  • Import Organization: Imports have been reordered and new utility imports (e.g., JsonIgnore, JsonAnyGetter, Logger) have been added to various model classes, enhancing code structure and maintainability.
  • Javadoc Refinements: Javadoc comments have been adjusted for conciseness and clarity, particularly in @param and @return tags, and formatting of multi-line expressions in equals and hashCode methods has been standardized.

🧠 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 pull request contains automated changes from a code generator. The changes are mostly stylistic, improving formatting and consistency across the codebase. However, I've noticed a recurring issue in the generated equals methods, where an unnecessary trailing semicolon is added. This seems to be a bug in the generator and should be fixed to improve code quality.

Objects.equals(this.requestedLevel, accountCapabilityData.requestedLevel) &&
Objects.equals(this.verificationDeadline, accountCapabilityData.verificationDeadline) &&
Objects.equals(this.verificationStatus, accountCapabilityData.verificationStatus)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.legalEntityId, accountCreateNotificationData.legalEntityId) &&
Objects.equals(this.merchantId, accountCreateNotificationData.merchantId) &&
Objects.equals(this.status, accountCreateNotificationData.status)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

return Objects.equals(
this.notificationResponse, accountNotificationResponse.notificationResponse);
return Objects.equals(this.notificationResponse, accountNotificationResponse.notificationResponse)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.legalEntityId, accountUpdateNotificationData.legalEntityId) &&
Objects.equals(this.merchantId, accountUpdateNotificationData.merchantId) &&
Objects.equals(this.status, accountUpdateNotificationData.status)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

&& Objects.equals(this.verificationErrors, capabilityProblem.verificationErrors);
return Objects.equals(this.entity, capabilityProblem.entity) &&
Objects.equals(this.verificationErrors, capabilityProblem.verificationErrors)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.terminalId, terminalSettingsData.terminalId) &&
Objects.equals(this.updateSource, terminalSettingsData.updateSource) &&
Objects.equals(this.user, terminalSettingsData.user)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.data, terminalSettingsNotificationRequest.data) &&
Objects.equals(this.environment, terminalSettingsNotificationRequest.environment) &&
Objects.equals(this.type, terminalSettingsNotificationRequest.type)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

this.notificationResponse, terminalSettingsNotificationResponse.notificationResponse);
TerminalSettingsNotificationResponse terminalSettingsNotificationResponse = (TerminalSettingsNotificationResponse) o;
return Objects.equals(this.notificationResponse, terminalSettingsNotificationResponse.notificationResponse)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.remediatingActions, verificationError.remediatingActions) &&
Objects.equals(this.subErrors, verificationError.subErrors) &&
Objects.equals(this.type, verificationError.type)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

Objects.equals(this.message, verificationErrorRecursive.message) &&
Objects.equals(this.type, verificationErrorRecursive.type) &&
Objects.equals(this.remediatingActions, verificationErrorRecursive.remediatingActions)
;
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 trailing semicolon on this line is unnecessary and can be removed. It creates an empty statement which has no effect and can be confusing.

@AdyenAutomationBot AdyenAutomationBot force-pushed the sdk-automation/managementwebhooks branch 3 times, most recently from 1ea31ea to ad5adf2 Compare January 8, 2026 12:04
@AdyenAutomationBot AdyenAutomationBot force-pushed the sdk-automation/managementwebhooks branch from 67d8273 to 0b79c23 Compare January 8, 2026 14:34
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