[negativebalancewarningwebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the negativebalancewarningwebhooks service.

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

[gemini-code-assist]

Summary of Changes

Hello @AdyenAutomationBot, I'm Gemini Code Assist¹! 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 an automated update to the negativebalancewarningwebhooks service's generated code. The changes primarily stem from an adyen-openapi commit, leading to a refresh of the service models and related utility classes. The modifications encompass updated imports, minor code formatting, and Javadoc refinements, ensuring the generated code remains consistent with the latest OpenAPI specification and generation tooling.

Highlights

• Automated Code Generation Update: This pull request is an automated update to the negativebalancewarningwebhooks service, reflecting recent changes in the adyen-openapi specification.
• Dependency and Import Adjustments: Several model files have updated imports, including new Jackson annotations (JsonIgnore, JsonAnyGetter, JsonCreator, JsonTypeName, JsonValue) and utility classes (Logger, Arrays), indicating a refresh of the OpenAPI Generator's output structure.
• Code Formatting and Javadoc Refinements: Minor formatting adjustments, such as whitespace, indentation, and Javadoc comment phrasing, have been applied across the generated Java classes to align with updated code generation standards.

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

[gemini-code-assist]

Code Review

This pull request appears to be an automated update from a code generator. The changes are primarily focused on code formatting, import organization, and Javadoc updates. While most changes align with standard Java conventions, I've noticed a recurring formatting issue in the equals methods across several model classes. A trailing semicolon is placed on a new line, which is unconventional and impacts readability. I've left specific comments with suggestions to correct this formatting. Since this is generated code, this feedback might be more relevant for the team managing the code generator.

[gemini-code-assist]

The formatting of this return statement is unconventional, particularly the trailing semicolon on a new line. This harms readability and deviates from standard Java coding practices. It should be refactored for clarity. Since this is auto-generated code, this might be an issue in the generator itself.

Suggested change

	return Objects.equals(this.currency, amount.currency) &&
	Objects.equals(this.value, amount.value)
	;
	return Objects.equals(this.currency, amount.currency) &&
	Objects.equals(this.value, amount.value);

[gemini-code-assist]

The formatting of this return statement is unconventional, particularly the trailing semicolon on a new line. This harms readability and deviates from standard Java coding practices. It should be refactored for clarity. Since this is auto-generated code, this might be an issue in the generator itself.

Suggested change

	return Objects.equals(this.accountHolder, negativeBalanceCompensationWarningNotificationData.accountHolder) &&
	Objects.equals(this.amount, negativeBalanceCompensationWarningNotificationData.amount) &&
	Objects.equals(this.balancePlatform, negativeBalanceCompensationWarningNotificationData.balancePlatform) &&
	Objects.equals(this.creationDate, negativeBalanceCompensationWarningNotificationData.creationDate) &&
	Objects.equals(this.id, negativeBalanceCompensationWarningNotificationData.id) &&
	Objects.equals(this.liableBalanceAccountId, negativeBalanceCompensationWarningNotificationData.liableBalanceAccountId) &&
	Objects.equals(this.negativeBalanceSince, negativeBalanceCompensationWarningNotificationData.negativeBalanceSince) &&
	Objects.equals(this.scheduledCompensationAt, negativeBalanceCompensationWarningNotificationData.scheduledCompensationAt)
	;
	return Objects.equals(this.accountHolder, negativeBalanceCompensationWarningNotificationData.accountHolder) &&
	Objects.equals(this.amount, negativeBalanceCompensationWarningNotificationData.amount) &&
	Objects.equals(this.balancePlatform, negativeBalanceCompensationWarningNotificationData.balancePlatform) &&
	Objects.equals(this.creationDate, negativeBalanceCompensationWarningNotificationData.creationDate) &&
	Objects.equals(this.id, negativeBalanceCompensationWarningNotificationData.id) &&
	Objects.equals(this.liableBalanceAccountId, negativeBalanceCompensationWarningNotificationData.liableBalanceAccountId) &&
	Objects.equals(this.negativeBalanceSince, negativeBalanceCompensationWarningNotificationData.negativeBalanceSince) &&
	Objects.equals(this.scheduledCompensationAt, negativeBalanceCompensationWarningNotificationData.scheduledCompensationAt);

[gemini-code-assist]

The formatting of this return statement is unconventional, particularly the trailing semicolon on a new line. This harms readability and deviates from standard Java coding practices. It should be refactored for clarity. Since this is auto-generated code, this might be an issue in the generator itself.

Suggested change

	return Objects.equals(this.data, negativeBalanceCompensationWarningNotificationRequest.data) &&
	Objects.equals(this.environment, negativeBalanceCompensationWarningNotificationRequest.environment) &&
	Objects.equals(this.timestamp, negativeBalanceCompensationWarningNotificationRequest.timestamp) &&
	Objects.equals(this.type, negativeBalanceCompensationWarningNotificationRequest.type)
	;
	return Objects.equals(this.data, negativeBalanceCompensationWarningNotificationRequest.data) &&
	Objects.equals(this.environment, negativeBalanceCompensationWarningNotificationRequest.environment) &&
	Objects.equals(this.timestamp, negativeBalanceCompensationWarningNotificationRequest.timestamp) &&
	Objects.equals(this.type, negativeBalanceCompensationWarningNotificationRequest.type);

[gemini-code-assist]

The formatting of this return statement is unconventional, particularly the trailing semicolon on a new line. This harms readability and deviates from standard Java coding practices. It should be refactored for clarity. Since this is auto-generated code, this might be an issue in the generator itself.

Suggested change

	return Objects.equals(this.balancePlatform, resource.balancePlatform) &&
	Objects.equals(this.creationDate, resource.creationDate) &&
	Objects.equals(this.id, resource.id)
	;
	return Objects.equals(this.balancePlatform, resource.balancePlatform) &&
	Objects.equals(this.creationDate, resource.creationDate) &&
	Objects.equals(this.id, resource.id);

[gemini-code-assist]

The formatting of this return statement is unconventional, particularly the trailing semicolon on a new line. This harms readability and deviates from standard Java coding practices. It should be refactored for clarity. Since this is auto-generated code, this might be an issue in the generator itself.

Suggested change

	return Objects.equals(this.description, resourceReference.description) &&
	Objects.equals(this.id, resourceReference.id) &&
	Objects.equals(this.reference, resourceReference.reference)
	;
	return Objects.equals(this.description, resourceReference.description) &&
	Objects.equals(this.id, resourceReference.id) &&
	Objects.equals(this.reference, resourceReference.reference);