Skip to content

[disputes] Code generation: update services and models#452

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

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

Conversation

@AdyenAutomationBot
Copy link
Collaborator

This PR contains the automated changes for the disputes service.

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

@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 automated updates to the disputes service API client. The primary goal is to enhance code maintainability and readability by modernizing string formatting for API endpoints and streamlining the syntax for API method invocations. These changes ensure the client library aligns with current best practices and the latest service definitions.

Highlights

  • Endpoint URL Formatting: Updated the construction of endpoint URLs from string concatenation to f-strings for improved readability and consistency.
  • API Call Refactoring: Simplified the self.client.call_adyen_api method calls by removing unnecessary line breaks, making the code more concise.
  • Automated Code Generation: Incorporated automated code generation updates for the disputes service, ensuring the API client remains current with the latest Adyen OpenAPI specifications.

🧠 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 disputes service, primarily updating endpoint string construction to use f-strings and reformatting method calls. While the intent seems to be modernization, the implementation has introduced some code style issues. The use of f-strings is not idiomatic in its current form, and the reformatting of call_adyen_api calls has resulted in lines that are excessively long, harming readability. My review includes suggestions to address these points by using f-strings more effectively and restoring the multi-line formatting for long method calls to adhere to common style practices.

Accept a dispute
"""
endpoint = self.baseUrl + "/acceptDispute"
endpoint = self.baseUrl + f"/acceptDispute"
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 prefix on this string literal is redundant as there are no expressions to interpolate. This can be confusing for developers. For constructing URLs, it's more idiomatic to include the base URL variable within the f-string itself for better readability.

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

return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line has become excessively long (over 100 characters), which harms readability and violates common Python style guidelines like PEP 8. The previous multi-line formatting was preferable. Please consider reformatting this call to span multiple lines.

Suggested change
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)

Defend a dispute
"""
endpoint = self.baseUrl + "/defendDispute"
endpoint = self.baseUrl + f"/defendDispute"
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 prefix on this string literal is redundant as there are no expressions to interpolate. This can be confusing for developers. For constructing URLs, it's more idiomatic to include the base URL variable within the f-string itself for better readability.

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

return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line has become excessively long (over 100 characters), which harms readability and violates common Python style guidelines like PEP 8. The previous multi-line formatting was preferable. Please consider reformatting this call to span multiple lines.

Suggested change
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)

Delete a defense document
"""
endpoint = self.baseUrl + "/deleteDisputeDefenseDocument"
endpoint = self.baseUrl + f"/deleteDisputeDefenseDocument"
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 prefix on this string literal is redundant as there are no expressions to interpolate. This can be confusing for developers. For constructing URLs, it's more idiomatic to include the base URL variable within the f-string itself for better readability.

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

return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line has become excessively long (over 100 characters), which harms readability and violates common Python style guidelines like PEP 8. The previous multi-line formatting was preferable. Please consider reformatting this call to span multiple lines.

Suggested change
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)

Get applicable defense reasons
"""
endpoint = self.baseUrl + "/retrieveApplicableDefenseReasons"
endpoint = self.baseUrl + f"/retrieveApplicableDefenseReasons"
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 prefix on this string literal is redundant as there are no expressions to interpolate. This can be confusing for developers. For constructing URLs, it's more idiomatic to include the base URL variable within the f-string itself for better readability.

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

return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line has become excessively long (over 100 characters), which harms readability and violates common Python style guidelines like PEP 8. The previous multi-line formatting was preferable. Please consider reformatting this call to span multiple lines.

Suggested change
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)

Supply a defense document
"""
endpoint = self.baseUrl + "/supplyDefenseDocument"
endpoint = self.baseUrl + f"/supplyDefenseDocument"
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 prefix on this string literal is redundant as there are no expressions to interpolate. This can be confusing for developers. For constructing URLs, it's more idiomatic to include the base URL variable within the f-string itself for better readability.

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

return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line has become excessively long (over 100 characters), which harms readability and violates common Python style guidelines like PEP 8. The previous multi-line formatting was preferable. Please consider reformatting this call to span multiple lines.

Suggested change
return self.client.call_adyen_api(request, self.service, method, endpoint, idempotency_key, **kwargs)
return self.client.call_adyen_api(
request, self.service, method, endpoint, idempotency_key, **kwargs
)

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