v6 - Enable logging for example integrations

[OscarSpruit]

Description

Enable verbose logging for v6 example integrations

[gemini-code-assist]

Summary of Changes

Hello @OscarSpruit, 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 focuses on enhancing the debuggability of the v6 example integrations by activating verbose logging across both the updated and older Adyen logging mechanisms. This ensures that developers and testers have access to comprehensive log output, which is crucial for troubleshooting and understanding the application's behavior during development.

Highlights

• Logging Configuration: Verbose logging has been explicitly enabled for both the new common Adyen logging framework and the legacy Adyen logging system within the example application.
• Import Management: To facilitate the simultaneous use of both logging frameworks, aliases (OldAdyenLogLevel and OldAdyenLogger) were introduced for the legacy logging classes, preventing naming conflicts with the new common logging imports.

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 enables verbose logging for the example integrations by setting the log level for both the old and new Adyen logger implementations. The change is straightforward and correct. I have one suggestion to improve code structure by moving the initialization logic to a more conventional location within the Android application lifecycle.

[github-actions]

✅ No public API changes

[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