[legalentitymanagement] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the legalentitymanagement 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 legalentitymanagement service's Java models and services. The changes primarily focus on maintaining up-to-date code generation, with a significant enhancement to how polymorphic types are handled in bank account identification, alongside general code formatting improvements across various model classes.

Highlights

• Code Generation Update: This pull request updates the generated Java services and models for the legalentitymanagement API, ensuring consistency with the latest OpenAPI specification.
• Improved Polymorphic Deserialization: The BankAccountInfoAccountIdentification class now includes custom JSON serializers and deserializers to correctly handle polymorphic types for various local account identifications (e.g., AU, CA, CZ, DK, HK, HU, IBAN, NO, NZ, PL, SE, SG, UK, US), enhancing data integrity and flexibility.
• Code Formatting and Javadoc Alignment: Numerous files received minor formatting adjustments, including reordering import statements, standardizing blank lines, and refining Javadoc comments for improved readability and adherence to 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 contains automated changes from a code generator. While most changes are formatting-related, I've identified a few recurring issues that affect code quality and should be addressed in the generator for future runs. These include superfluous trailing semicolons in equals methods, a missing newline character at the end of one file, and a duplicate import. My specific comments highlight these points.

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct in Java (it's an empty statement), it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.accountNumber, auLocalAccountIdentification.accountNumber) &&
	Objects.equals(this.isSetAccountNumber, auLocalAccountIdentification.isSetAccountNumber) &&
	Objects.equals(this.bsbCode, auLocalAccountIdentification.bsbCode) &&
	Objects.equals(this.isSetBsbCode, auLocalAccountIdentification.isSetBsbCode) &&
	Objects.equals(this.type, auLocalAccountIdentification.type) &&
	Objects.equals(this.isSetType, auLocalAccountIdentification.isSetType)
	;
	return Objects.equals(this.accountNumber, auLocalAccountIdentification.accountNumber) &&
	Objects.equals(this.isSetAccountNumber, auLocalAccountIdentification.isSetAccountNumber) &&
	Objects.equals(this.bsbCode, auLocalAccountIdentification.bsbCode) &&
	Objects.equals(this.isSetBsbCode, auLocalAccountIdentification.isSetBsbCode) &&
	Objects.equals(this.type, auLocalAccountIdentification.type) &&
	Objects.equals(this.isSetType, auLocalAccountIdentification.isSetType);

[gemini-code-assist]

This file is missing a final newline character. It's a standard convention to end files with a newline to avoid issues with some tools and to improve readability when concatenating files.

[gemini-code-assist]

This import statement for com.fasterxml.jackson.core.type.TypeReference is a duplicate of the one on line 45. Please remove the redundant import to improve code quality.

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.acceptedBy, acceptTermsOfServiceRequest.acceptedBy) &&
	Objects.equals(this.isSetAcceptedBy, acceptTermsOfServiceRequest.isSetAcceptedBy) &&
	Objects.equals(this.ipAddress, acceptTermsOfServiceRequest.ipAddress) &&
	Objects.equals(this.isSetIpAddress, acceptTermsOfServiceRequest.isSetIpAddress)
	;
	return Objects.equals(this.acceptedBy, acceptTermsOfServiceRequest.acceptedBy) &&
	Objects.equals(this.isSetAcceptedBy, acceptTermsOfServiceRequest.isSetAcceptedBy) &&
	Objects.equals(this.ipAddress, acceptTermsOfServiceRequest.ipAddress) &&
	Objects.equals(this.isSetIpAddress, acceptTermsOfServiceRequest.isSetIpAddress);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.acceptedBy, acceptTermsOfServiceResponse.acceptedBy) &&
	Objects.equals(this.isSetAcceptedBy, acceptTermsOfServiceResponse.isSetAcceptedBy) &&
	Objects.equals(this.id, acceptTermsOfServiceResponse.id) &&
	Objects.equals(this.isSetId, acceptTermsOfServiceResponse.isSetId) &&
	Objects.equals(this.ipAddress, acceptTermsOfServiceResponse.ipAddress) &&
	Objects.equals(this.isSetIpAddress, acceptTermsOfServiceResponse.isSetIpAddress) &&
	Objects.equals(this.language, acceptTermsOfServiceResponse.language) &&
	Objects.equals(this.isSetLanguage, acceptTermsOfServiceResponse.isSetLanguage) &&
	Objects.equals(this.termsOfServiceDocumentId, acceptTermsOfServiceResponse.termsOfServiceDocumentId) &&
	Objects.equals(this.isSetTermsOfServiceDocumentId, acceptTermsOfServiceResponse.isSetTermsOfServiceDocumentId) &&
	Objects.equals(this.type, acceptTermsOfServiceResponse.type) &&
	Objects.equals(this.isSetType, acceptTermsOfServiceResponse.isSetType)
	;
	return Objects.equals(this.acceptedBy, acceptTermsOfServiceResponse.acceptedBy) &&
	Objects.equals(this.isSetAcceptedBy, acceptTermsOfServiceResponse.isSetAcceptedBy) &&
	Objects.equals(this.id, acceptTermsOfServiceResponse.id) &&
	Objects.equals(this.isSetId, acceptTermsOfServiceResponse.isSetId) &&
	Objects.equals(this.ipAddress, acceptTermsOfServiceResponse.ipAddress) &&
	Objects.equals(this.isSetIpAddress, acceptTermsOfServiceResponse.isSetIpAddress) &&
	Objects.equals(this.language, acceptTermsOfServiceResponse.language) &&
	Objects.equals(this.isSetLanguage, acceptTermsOfServiceResponse.isSetLanguage) &&
	Objects.equals(this.termsOfServiceDocumentId, acceptTermsOfServiceResponse.termsOfServiceDocumentId) &&
	Objects.equals(this.isSetTermsOfServiceDocumentId, acceptTermsOfServiceResponse.isSetTermsOfServiceDocumentId) &&
	Objects.equals(this.type, acceptTermsOfServiceResponse.type) &&
	Objects.equals(this.isSetType, acceptTermsOfServiceResponse.isSetType);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.cardNumber, identificationData.cardNumber) &&
	Objects.equals(this.isSetCardNumber, identificationData.isSetCardNumber) &&
	Objects.equals(this.expiryDate, identificationData.expiryDate) &&
	Objects.equals(this.isSetExpiryDate, identificationData.isSetExpiryDate) &&
	Objects.equals(this.issuerCountry, identificationData.issuerCountry) &&
	Objects.equals(this.isSetIssuerCountry, identificationData.isSetIssuerCountry) &&
	Objects.equals(this.issuerState, identificationData.issuerState) &&
	Objects.equals(this.isSetIssuerState, identificationData.isSetIssuerState) &&
	Objects.equals(this.nationalIdExempt, identificationData.nationalIdExempt) &&
	Objects.equals(this.isSetNationalIdExempt, identificationData.isSetNationalIdExempt) &&
	Objects.equals(this.number, identificationData.number) &&
	Objects.equals(this.isSetNumber, identificationData.isSetNumber) &&
	Objects.equals(this.type, identificationData.type) &&
	Objects.equals(this.isSetType, identificationData.isSetType)
	;
	return Objects.equals(this.cardNumber, identificationData.cardNumber) &&
	Objects.equals(this.isSetCardNumber, identificationData.isSetCardNumber) &&
	Objects.equals(this.expiryDate, identificationData.expiryDate) &&
	Objects.equals(this.isSetExpiryDate, identificationData.isSetExpiryDate) &&
	Objects.equals(this.issuerCountry, identificationData.issuerCountry) &&
	Objects.equals(this.isSetIssuerCountry, identificationData.isSetIssuerCountry) &&
	Objects.equals(this.issuerState, identificationData.issuerState) &&
	Objects.equals(this.isSetIssuerState, identificationData.isSetIssuerState) &&
	Objects.equals(this.nationalIdExempt, identificationData.nationalIdExempt) &&
	Objects.equals(this.isSetNationalIdExempt, identificationData.isSetNationalIdExempt) &&
	Objects.equals(this.number, identificationData.number) &&
	Objects.equals(this.isSetNumber, identificationData.isSetNumber) &&
	Objects.equals(this.type, identificationData.type) &&
	Objects.equals(this.isSetType, identificationData.isSetType);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.birthData, individual.birthData) &&
	Objects.equals(this.isSetBirthData, individual.isSetBirthData) &&
	Objects.equals(this.email, individual.email) &&
	Objects.equals(this.isSetEmail, individual.isSetEmail) &&
	Objects.equals(this.identificationData, individual.identificationData) &&
	Objects.equals(this.isSetIdentificationData, individual.isSetIdentificationData) &&
	Objects.equals(this.name, individual.name) &&
	Objects.equals(this.isSetName, individual.isSetName) &&
	Objects.equals(this.nationality, individual.nationality) &&
	Objects.equals(this.isSetNationality, individual.isSetNationality) &&
	Objects.equals(this.phone, individual.phone) &&
	Objects.equals(this.isSetPhone, individual.isSetPhone) &&
	Objects.equals(this.residentialAddress, individual.residentialAddress) &&
	Objects.equals(this.isSetResidentialAddress, individual.isSetResidentialAddress) &&
	Objects.equals(this.support, individual.support) &&
	Objects.equals(this.isSetSupport, individual.isSetSupport) &&
	Objects.equals(this.taxInformation, individual.taxInformation) &&
	Objects.equals(this.isSetTaxInformation, individual.isSetTaxInformation) &&
	Objects.equals(this.webData, individual.webData) &&
	Objects.equals(this.isSetWebData, individual.isSetWebData)
	;
	return Objects.equals(this.birthData, individual.birthData) &&
	Objects.equals(this.isSetBirthData, individual.isSetBirthData) &&
	Objects.equals(this.email, individual.email) &&
	Objects.equals(this.isSetEmail, individual.isSetEmail) &&
	Objects.equals(this.identificationData, individual.identificationData) &&
	Objects.equals(this.isSetIdentificationData, individual.isSetIdentificationData) &&
	Objects.equals(this.name, individual.name) &&
	Objects.equals(this.isSetName, individual.isSetName) &&
	Objects.equals(this.nationality, individual.nationality) &&
	Objects.equals(this.isSetNationality, individual.isSetNationality) &&
	Objects.equals(this.phone, individual.phone) &&
	Objects.equals(this.isSetPhone, individual.isSetPhone) &&
	Objects.equals(this.residentialAddress, individual.residentialAddress) &&
	Objects.equals(this.isSetResidentialAddress, individual.isSetResidentialAddress) &&
	Objects.equals(this.support, individual.support) &&
	Objects.equals(this.isSetSupport, individual.isSetSupport) &&
	Objects.equals(this.taxInformation, individual.taxInformation) &&
	Objects.equals(this.isSetTaxInformation, individual.isSetTaxInformation) &&
	Objects.equals(this.webData, individual.webData) &&
	Objects.equals(this.isSetWebData, individual.isSetWebData);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

    return Objects.equals(this.capabilities, legalEntity.capabilities) &&
        Objects.equals(this.isSetCapabilities, legalEntity.isSetCapabilities) &&
        Objects.equals(this.documentDetails, legalEntity.documentDetails) &&
        Objects.equals(this.isSetDocumentDetails, legalEntity.isSetDocumentDetails) &&
        Objects.equals(this.documents, legalEntity.documents) &&
        Objects.equals(this.isSetDocuments, legalEntity.isSetDocuments) &&
        Objects.equals(this.entityAssociations, legalEntity.entityAssociations) &&
        Objects.equals(this.isSetEntityAssociations, legalEntity.isSetEntityAssociations) &&
        Objects.equals(this.id, legalEntity.id) &&
        Objects.equals(this.isSetId, legalEntity.isSetId) &&
        Objects.equals(this.individual, legalEntity.individual) &&
        Objects.equals(this.isSetIndividual, legalEntity.isSetIndividual) &&
        Objects.equals(this.organization, legalEntity.organization) &&
        Objects.equals(this.isSetOrganization, legalEntity.isSetOrganization) &&
        Objects.equals(this.problems, legalEntity.problems) &&
        Objects.equals(this.isSetProblems, legalEntity.isSetProblems) &&
        Objects.equals(this.reference, legalEntity.reference) &&
        Objects.equals(this.isSetReference, legalEntity.isSetReference) &&
        Objects.equals(this.soleProprietorship, legalEntity.soleProprietorship) &&
        Objects.equals(this.isSetSoleProprietorship, legalEntity.isSetSoleProprietorship) &&
        Objects.equals(this.transferInstruments, legalEntity.transferInstruments) &&
        Objects.equals(this.isSetTransferInstruments, legalEntity.isSetTransferInstruments) &&
        Objects.equals(this.trust, legalEntity.trust) &&
        Objects.equals(this.isSetTrust, legalEntity.isSetTrust) &&
        Objects.equals(this.type, legalEntity.type) &&
        Objects.equals(this.isSetType, legalEntity.isSetType) &&
        Objects.equals(this.unincorporatedPartnership, legalEntity.unincorporatedPartnership) &&
        Objects.equals(this.isSetUnincorporatedPartnership, legalEntity.isSetUnincorporatedPartnership) &&
        Objects.equals(this.verificationDeadlines, legalEntity.verificationDeadlines) &&
        Objects.equals(this.isSetVerificationDeadlines, legalEntity.isSetVerificationDeadlines) &&
        Objects.equals(this.verificationPlan, legalEntity.verificationPlan) &&
        Objects.equals(this.isSetVerificationPlan, legalEntity.isSetVerificationPlan);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.associatorId, legalEntityAssociation.associatorId) &&
	Objects.equals(this.isSetAssociatorId, legalEntityAssociation.isSetAssociatorId) &&
	Objects.equals(this.entityType, legalEntityAssociation.entityType) &&
	Objects.equals(this.isSetEntityType, legalEntityAssociation.isSetEntityType) &&
	Objects.equals(this.jobTitle, legalEntityAssociation.jobTitle) &&
	Objects.equals(this.isSetJobTitle, legalEntityAssociation.isSetJobTitle) &&
	Objects.equals(this.legalEntityId, legalEntityAssociation.legalEntityId) &&
	Objects.equals(this.isSetLegalEntityId, legalEntityAssociation.isSetLegalEntityId) &&
	Objects.equals(this.name, legalEntityAssociation.name) &&
	Objects.equals(this.isSetName, legalEntityAssociation.isSetName) &&
	Objects.equals(this.nominee, legalEntityAssociation.nominee) &&
	Objects.equals(this.isSetNominee, legalEntityAssociation.isSetNominee) &&
	Objects.equals(this.relationship, legalEntityAssociation.relationship) &&
	Objects.equals(this.isSetRelationship, legalEntityAssociation.isSetRelationship) &&
	Objects.equals(this.settlorExemptionReason, legalEntityAssociation.settlorExemptionReason) &&
	Objects.equals(this.isSetSettlorExemptionReason, legalEntityAssociation.isSetSettlorExemptionReason) &&
	Objects.equals(this.type, legalEntityAssociation.type) &&
	Objects.equals(this.isSetType, legalEntityAssociation.isSetType)
	;
	return Objects.equals(this.associatorId, legalEntityAssociation.associatorId) &&
	Objects.equals(this.isSetAssociatorId, legalEntityAssociation.isSetAssociatorId) &&
	Objects.equals(this.entityType, legalEntityAssociation.entityType) &&
	Objects.equals(this.isSetEntityType, legalEntityAssociation.isSetEntityType) &&
	Objects.equals(this.jobTitle, legalEntityAssociation.jobTitle) &&
	Objects.equals(this.isSetJobTitle, legalEntityAssociation.isSetJobTitle) &&
	Objects.equals(this.legalEntityId, legalEntityAssociation.legalEntityId) &&
	Objects.equals(this.isSetLegalEntityId, legalEntityAssociation.isSetLegalEntityId) &&
	Objects.equals(this.name, legalEntityAssociation.name) &&
	Objects.equals(this.isSetName, legalEntityAssociation.isSetName) &&
	Objects.equals(this.nominee, legalEntityAssociation.nominee) &&
	Objects.equals(this.isSetNominee, legalEntityAssociation.isSetNominee) &&
	Objects.equals(this.relationship, legalEntityAssociation.relationship) &&
	Objects.equals(this.isSetRelationship, legalEntityAssociation.isSetRelationship) &&
	Objects.equals(this.settlorExemptionReason, legalEntityAssociation.settlorExemptionReason) &&
	Objects.equals(this.isSetSettlorExemptionReason, legalEntityAssociation.isSetSettlorExemptionReason) &&
	Objects.equals(this.type, legalEntityAssociation.type) &&
	Objects.equals(this.isSetType, legalEntityAssociation.isSetType);

[gemini-code-assist]

The equals method implementation ends with a superfluous trailing semicolon. While syntactically correct, it serves no purpose and can be confusing. This appears to be a code generation issue and is present in multiple files in this pull request. Please remove it for better code clarity.

Suggested change

	return Objects.equals(this.allowed, legalEntityCapability.allowed) &&
	Objects.equals(this.isSetAllowed, legalEntityCapability.isSetAllowed) &&
	Objects.equals(this.allowedLevel, legalEntityCapability.allowedLevel) &&
	Objects.equals(this.isSetAllowedLevel, legalEntityCapability.isSetAllowedLevel) &&
	Objects.equals(this.allowedSettings, legalEntityCapability.allowedSettings) &&
	Objects.equals(this.isSetAllowedSettings, legalEntityCapability.isSetAllowedSettings) &&
	Objects.equals(this.requested, legalEntityCapability.requested) &&
	Objects.equals(this.isSetRequested, legalEntityCapability.isSetRequested) &&
	Objects.equals(this.requestedLevel, legalEntityCapability.requestedLevel) &&
	Objects.equals(this.isSetRequestedLevel, legalEntityCapability.isSetRequestedLevel) &&
	Objects.equals(this.requestedSettings, legalEntityCapability.requestedSettings) &&
	Objects.equals(this.isSetRequestedSettings, legalEntityCapability.isSetRequestedSettings) &&
	Objects.equals(this.transferInstruments, legalEntityCapability.transferInstruments) &&
	Objects.equals(this.isSetTransferInstruments, legalEntityCapability.isSetTransferInstruments) &&
	Objects.equals(this.verificationStatus, legalEntityCapability.verificationStatus) &&
	Objects.equals(this.isSetVerificationStatus, legalEntityCapability.isSetVerificationStatus)
	;
	return Objects.equals(this.allowed, legalEntityCapability.allowed) &&
	Objects.equals(this.isSetAllowed, legalEntityCapability.isSetAllowed) &&
	Objects.equals(this.allowedLevel, legalEntityCapability.allowedLevel) &&
	Objects.equals(this.isSetAllowedLevel, legalEntityCapability.isSetAllowedLevel) &&
	Objects.equals(this.allowedSettings, legalEntityCapability.allowedSettings) &&
	Objects.equals(this.isSetAllowedSettings, legalEntityCapability.isSetAllowedSettings) &&
	Objects.equals(this.requested, legalEntityCapability.requested) &&
	Objects.equals(this.isSetRequested, legalEntityCapability.isSetRequested) &&
	Objects.equals(this.requestedLevel, legalEntityCapability.requestedLevel) &&
	Objects.equals(this.isSetRequestedLevel, legalEntityCapability.isSetRequestedLevel) &&
	Objects.equals(this.requestedSettings, legalEntityCapability.requestedSettings) &&
	Objects.equals(this.isSetRequestedSettings, legalEntityCapability.isSetRequestedSettings) &&
	Objects.equals(this.transferInstruments, legalEntityCapability.transferInstruments) &&
	Objects.equals(this.isSetTransferInstruments, legalEntityCapability.isSetTransferInstruments) &&
	Objects.equals(this.verificationStatus, legalEntityCapability.verificationStatus) &&
	Objects.equals(this.isSetVerificationStatus, legalEntityCapability.isSetVerificationStatus);