Skip to content

[legalentitymanagement] Code generation: update services and models#456

Open
AdyenAutomationBot wants to merge 1 commit intomainfrom
sdk-automation/legalentitymanagement
Open

[legalentitymanagement] Code generation: update services and models#456
AdyenAutomationBot wants to merge 1 commit intomainfrom
sdk-automation/legalentitymanagement

Conversation

@AdyenAutomationBot
Copy link
Collaborator

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.

@AdyenAutomationBot AdyenAutomationBot requested review from a team as code owners March 20, 2026 10:37
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 an automated update to the legalentitymanagement service, primarily focusing on standardizing the formatting of API client method calls and modernizing endpoint URL construction. These changes streamline the codebase, making it more consistent and easier to maintain, without altering the functional behavior of the API interactions.

Highlights

  • Code Generation Update: The pull request introduces automated updates to the legalentitymanagement service, ensuring the API client remains synchronized with the latest adyen-openapi specifications.
  • Code Formatting Standardization: All call_adyen_api method invocations across various API files have been reformatted to occupy a single line, improving code conciseness and readability.
  • Endpoint URL Construction: Endpoint URL string concatenations have been consistently updated to use Python's f-string syntax, enhancing clarity and modernizing the codebase.

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

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.

@sonarqubecloud
Copy link

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 introduces automated changes to the legalentitymanagement service, primarily focused on code formatting. The changes involve converting multi-line statements into single lines and updating string concatenations for URL endpoints. While the formatting changes are consistent, I've noticed a recurring pattern where f-strings are used unnecessarily on static strings. I have left comments with suggestions to use f-strings more idiomatically for constructing URLs, which will improve code clarity and maintainability.

Create a business line
"""
endpoint = self.baseUrl + "/businessLines"
endpoint = self.baseUrl + f"/businessLines"
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 f-string f"/businessLines" is unnecessary as it doesn't contain any expressions. A more idiomatic way to construct the URL would be to use a single f-string for the entire expression.

Suggested change
endpoint = self.baseUrl + f"/businessLines"
endpoint = f"{self.baseUrl}/businessLines"

Upload a document for verification checks
"""
endpoint = self.baseUrl + "/documents"
endpoint = self.baseUrl + f"/documents"
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 f-string f"/documents" is unnecessary as it doesn't contain any expressions. A more idiomatic way to construct the URL would be to use a single f-string for the entire expression.

Suggested change
endpoint = self.baseUrl + f"/documents"
endpoint = f"{self.baseUrl}/documents"

Get a list of hosted onboarding page themes
"""
endpoint = self.baseUrl + "/themes"
endpoint = self.baseUrl + f"/themes"
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 f-string f"/themes" is unnecessary as it doesn't contain any expressions. A more idiomatic way to construct the URL would be to use a single f-string for the entire expression.

Suggested change
endpoint = self.baseUrl + f"/themes"
endpoint = f"{self.baseUrl}/themes"

Create a legal entity
"""
endpoint = self.baseUrl + "/legalEntities"
endpoint = self.baseUrl + f"/legalEntities"
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 f-string f"/legalEntities" is unnecessary as it doesn't contain any expressions. A more idiomatic way to construct the URL would be to use a single f-string for the entire expression.

Suggested change
endpoint = self.baseUrl + f"/legalEntities"
endpoint = f"{self.baseUrl}/legalEntities"

Create a transfer instrument
"""
endpoint = self.baseUrl + "/transferInstruments"
endpoint = self.baseUrl + f"/transferInstruments"
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 f-string f"/transferInstruments" is unnecessary as it doesn't contain any expressions. A more idiomatic way to construct the URL would be to use a single f-string for the entire expression.

Suggested change
endpoint = self.baseUrl + f"/transferInstruments"
endpoint = f"{self.baseUrl}/transferInstruments"

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.

1 participant