[recurring] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the recurring service.

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[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 incorporates automated code generation updates for the Adyen recurring service. The core change involves a renaming of the LegacyRecurringApi class to RecurringApi and subsequently updating its instantiation within the main recurring service file. This ensures the codebase remains consistent with the latest API definitions and generated structures.

Highlights

• Class Renaming: The LegacyRecurringApi class has been renamed to RecurringApi to align with updated code generation standards.
• Service Initialization Update: The recurring_api method in lib/adyen/services/recurring.rb was updated to initialize with the newly named RecurringApi class.

🧠 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

• lib/adyen/services/recurring.rb
  • Updated the class used for initializing the recurring_api instance from Adyen::LegacyRecurringApi to Adyen::RecurringApi.
• lib/adyen/services/recurring/recurring_api.rb
  • Renamed the class definition from LegacyRecurringApi to RecurringApi.

Activity

• Automated code generation changes were applied by AdyenAutomationBot.
• The commit history reflects updates originating from adyen-openapi.

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 that rename LegacyRecurringApi to RecurringApi. The changes are consistent across the class definition and its usage, which is a good step towards removing legacy naming conventions. The changes are straightforward and correct. I have no further comments.