BalancePlatform TransferLimits: update order of path params for deletePendingTransferLimit and getSpecificTransferLimit

[gcatanese]

PR to regenerate BalancePlatform TransferLimits services: the OpenAPI file has been updated to correct the order the path parameters, this PR (re)generates the service classes and corrects the tests.

[gemini-code-assist]

Summary of Changes

Hello @gcatanese, 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 addresses an inconsistency in the OpenAPI specification for the BalancePlatform TransferLimits service, specifically concerning the order of path parameters for certain API endpoints. The changes involve regenerating the affected Java service classes to correctly reflect the updated OpenAPI definition, ensuring that methods like deletePendingTransferLimit and getSpecificTransferLimit now accept parameters in the intended sequence. Additionally, the associated unit tests have been updated to align with these corrected method signatures and improve clarity in test data.

Highlights

• Service Regeneration: The BalancePlatform TransferLimits service has been regenerated to incorporate updates from the OpenAPI specification.
• Path Parameter Order Correction: The order of path parameters for the deletePendingTransferLimit and getSpecificTransferLimit methods has been corrected in both BalanceAccountLevelApi and BalancePlatformLevelApi.
• Javadoc Cleanup: Redundant @param tags were removed from Javadoc comments in the service classes.
• Test Updates: Corresponding test files have been updated to reflect the new parameter order and correct variable names, ensuring all API calls are made with the proper arguments.

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 updates the BalancePlatform TransferLimits service classes and tests to reflect a change in the OpenAPI specification, specifically correcting the order of path parameters for deletePendingTransferLimit and getSpecificTransferLimit methods. The changes are mostly generated and look correct, including updates to method signatures, Javadoc, and internal logic. The corresponding test files are also updated to match these changes. I've pointed out a few minor formatting inconsistencies in one of the test files that should be addressed for code style consistency.