[ECP-9487] Handle exceptions in AdyenLogger getInvoiceContext

[shubhamk67]

Description
This PR adds exception handling in AdyenLogger.getInvoiceContext() to allow webhook processing to continue in case of failures during logging by returning an empty context.

[gemini-code-assist]

Summary of Changes

Hello @shubhamk67, 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 enhances the robustness of the Adyen logging mechanism by introducing exception handling to the getInvoiceContext method. The primary goal is to prevent logging failures from disrupting critical processes, such as webhook handling. By catching potential errors and returning an empty context, the system ensures that operations can continue smoothly, improving overall stability and reliability.

Highlights

• Exception Handling: Implemented a try-catch block within the getInvoiceContext method of AdyenLogger.php to gracefully handle any exceptions that may occur during the retrieval of invoice context details.
• Webhook Processing Resilience: Ensures that webhook processing can continue uninterrupted even if an error occurs while generating the invoice context for logging purposes.
• Default Return Value: If an exception is caught, the getInvoiceContext method will now return an empty array, preventing a crash and allowing the main process to proceed.

🧠 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.

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 effectively prevents exceptions within AdyenLogger::getInvoiceContext from halting webhook processing by wrapping the logic in a try-catch block and returning an empty context on failure. This is a good improvement for robustness. My review includes a suggestion to log the caught exception to improve observability and make debugging easier, as silently swallowing exceptions can hide underlying issues.

[gemini-code-assist]

While catching the exception is a good step to prevent process interruption, it's also important to log that an exception occurred. Swallowing the exception silently can make it difficult to debug issues with logging context in the future. I suggest logging the exception message as a warning before returning the empty array.

        } catch (\Exception $e) {
            $this->addAdyenWarning('Failed to generate invoice context for logging: ' . $e->getMessage());
            return [];
        }

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud