[disputewebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the disputewebhooks 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 automated updates to the disputewebhooks service, primarily focusing on code generation aspects. The changes encompass a thorough reordering and addition of import statements, alongside general code formatting and whitespace adjustments across various model and utility classes. These modifications are crucial for maintaining consistency with the latest OpenAPI specification and generation standards, ensuring the codebase remains clean and up-to-date without altering the core business logic of the dispute webhooks.

Highlights

• Automated Code Generation Update: This pull request applies automated changes to the disputewebhooks service, indicating an update to the underlying OpenAPI specification or the code generation tool used.
• Import Statement Refinements: Across several Java model and utility classes, import statements have been reordered and new com.fasterxml.jackson.annotation and java.util imports have been added, enhancing code consistency and potentially leveraging new Jackson features.
• Code Formatting and Whitespace Adjustments: Numerous minor formatting changes, including added blank lines, adjusted Javadoc comments, and whitespace modifications within method bodies, have been applied to improve readability and adhere to updated coding 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 code generation update. The changes are mostly stylistic, but I've identified a couple of recurring formatting issues that seem to be bugs in the generator. Specifically, there's a stray semicolon in the equals methods and broken Javadoc comments for fromJson and toJson methods across several model files. Fixing these in the generator template would improve code quality and maintainability.

[gemini-code-assist]

There's a stray semicolon on a new line at the end of the return statement. While this is valid Java syntax (it's an empty statement), it's unconventional and harms readability. It should be removed. This seems to be a recurring issue in the generated code and might need a fix in the generator template.

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 Javadoc for fromJson has formatting issues, with extra newlines and incorrect indentation. The toJson method's Javadoc (starting on line 174) has a similar issue. This appears to be a problem with the code generator's template and should be fixed for consistency and readability.

[gemini-code-assist]

There's a stray semicolon on a new line at the end of the return statement. While this is valid Java syntax (it's an empty statement), it's unconventional and harms readability. It should be removed. This seems to be a recurring issue in the generated code and might need a fix in the generator template.

Suggested change

	return Objects.equals(this.notificationResponse, balancePlatformNotificationResponse.notificationResponse)
	;
	return Objects.equals(this.notificationResponse, balancePlatformNotificationResponse.notificationResponse);

[gemini-code-assist]

The Javadoc for fromJson has formatting issues, with extra newlines and incorrect indentation. The toJson method's Javadoc (starting on line 134) has a similar issue. This appears to be a problem with the code generator's template and should be fixed for consistency and readability.

[gemini-code-assist]

There's a stray semicolon on a new line at the end of the return statement. While this is valid Java syntax (it's an empty statement), it's unconventional and harms readability. It should be removed. This seems to be a recurring issue in the generated code and might need a fix in the generator template.

Suggested change

	return Objects.equals(this.arn, disputeEventNotification.arn) &&
	Objects.equals(this.balancePlatform, disputeEventNotification.balancePlatform) &&
	Objects.equals(this.creationDate, disputeEventNotification.creationDate) &&
	Objects.equals(this.description, disputeEventNotification.description) &&
	Objects.equals(this.disputedAmount, disputeEventNotification.disputedAmount) &&
	Objects.equals(this.id, disputeEventNotification.id) &&
	Objects.equals(this.status, disputeEventNotification.status) &&
	Objects.equals(this.statusDetail, disputeEventNotification.statusDetail) &&
	Objects.equals(this.transactionId, disputeEventNotification.transactionId) &&
	Objects.equals(this.type, disputeEventNotification.type)
	;
	return Objects.equals(this.arn, disputeEventNotification.arn) &&
	Objects.equals(this.balancePlatform, disputeEventNotification.balancePlatform) &&
	Objects.equals(this.creationDate, disputeEventNotification.creationDate) &&
	Objects.equals(this.description, disputeEventNotification.description) &&
	Objects.equals(this.disputedAmount, disputeEventNotification.disputedAmount) &&
	Objects.equals(this.id, disputeEventNotification.id) &&
	Objects.equals(this.status, disputeEventNotification.status) &&
	Objects.equals(this.statusDetail, disputeEventNotification.statusDetail) &&
	Objects.equals(this.transactionId, disputeEventNotification.transactionId) &&
	Objects.equals(this.type, disputeEventNotification.type);

[gemini-code-assist]

The Javadoc for fromJson has formatting issues, with extra newlines and incorrect indentation. The toJson method's Javadoc (starting on line 540) has a similar issue. This appears to be a problem with the code generator's template and should be fixed for consistency and readability.

[gemini-code-assist]

There's a stray semicolon on a new line at the end of the return statement. While this is valid Java syntax (it's an empty statement), it's unconventional and harms readability. It should be removed. This seems to be a recurring issue in the generated code and might need a fix in the generator template.

Suggested change

	return Objects.equals(this.data, disputeNotificationRequest.data) &&
	Objects.equals(this.type, disputeNotificationRequest.type)
	;
	return Objects.equals(this.data, disputeNotificationRequest.data) &&
	Objects.equals(this.type, disputeNotificationRequest.type);

[gemini-code-assist]

The Javadoc for fromJson has formatting issues, with extra newlines and incorrect indentation. The toJson method's Javadoc (starting on line 215) has a similar issue. This appears to be a problem with the code generator's template and should be fixed for consistency and readability.