Walkthrough

The change refactors WriteAsyncLogEvent to centralize async continuation wrapping by invoking PreventMultipleCalls once at the method's start, creating a wrapped log event, and consistently reusing it across initialization failure and success code paths instead of duplicating wrapping logic.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Key attention area: Verify that wrappedLogEvent is correctly constructed and that the wrapped continuation is properly applied across all code paths (initialization failure, initialization success, and standard execution).
• Concern: Ensure the refactoring doesn't inadvertently change behavior by comparing how the continuation was previously applied in duplicate locations versus the consolidated approach.

Poem

🐰 A hop through the logic, so clean and so tight,
One wrapping, one path, no duplication blight,
The continuation now flows without repeat,
Prevention of calls makes the logic complete! 🎯

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud