[balanceplatform] Code generation: update services and models#350
[balanceplatform] Code generation: update services and models#350AdyenAutomationBot wants to merge 1 commit intomainfrom
Conversation
Summary of ChangesHello @AdyenAutomationBot, 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 automates the update of services and models for the Highlights
🧠 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. Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces a new get_tax_form_summary method to the AccountHoldersApi, which appears to be an automated, generated change. The implementation is consistent with other methods in the file. My review includes a couple of suggestions to enhance code quality by addressing code duplication in endpoint construction and refining how query strings are generated. These improvements could be beneficial if applied more broadly, perhaps even to the code generator itself.
| endpoint = '/accountHolders/{id}/taxFormSummary'.gsub(/{.+?}/, '%s') | ||
| endpoint = endpoint.gsub(%r{^/}, '') | ||
| endpoint = format(endpoint, id) |
There was a problem hiding this comment.
This pattern for building the endpoint URL is duplicated across several methods in this class (e.g., get_account_holder, get_tax_form). To improve maintainability and reduce redundancy, consider extracting this logic into a private helper method.
For example:
private
def build_endpoint(path, *params)
endpoint = path.gsub(/{.+?}/, '%s').delete_prefix('/')
format(endpoint, *params)
endThis would allow you to simplify the implementation in this and other methods:
def get_tax_form_summary(id, headers: {}, query_params: {})
endpoint = build_endpoint('/accountHolders/{id}/taxFormSummary', id)
# ...
end| endpoint = '/accountHolders/{id}/taxFormSummary'.gsub(/{.+?}/, '%s') | ||
| endpoint = endpoint.gsub(%r{^/}, '') | ||
| endpoint = format(endpoint, id) | ||
| endpoint += create_query_string(query_params) |
There was a problem hiding this comment.
The create_query_string method appends a ? to the URL even when query_params is empty. While this is generally not a functional issue, it results in URLs with a trailing ? when no query parameters are provided. It would be cleaner to modify create_query_string to only append the query string when parameters are present.
Suggested change in lib/adyen/services/service.rb:
def create_query_string(params)
return '' if params.empty?
"?#{URI.encode_www_form(params)}"
end09c38c6 to
27bd9fb
Compare
27bd9fb to
a5ce7ad
Compare
|



This PR contains the automated changes for the
balanceplatformservice.The commit history of this PR reflects the
adyen-openapicommits that have been applied.