Unwrap HandlerFailedException and add AccessDeniedException to be caught#19
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
WalkthroughThis PR adds support for handling Symfony Messenger's Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant Messenger as Messenger Bus
participant Subscriber as ApiExceptionSubscriber
participant Transformer as DefaultExceptionToApiProblemTransformer
participant Response
Client->>Messenger: Handler execution
Messenger->>Messenger: Handler throws exception
Messenger->>Subscriber: Wraps in HandlerFailedException
Subscriber->>Subscriber: Detect HandlerFailedException
Subscriber->>Subscriber: Unwrap to underlying exception
Subscriber->>Transformer: Pass unwrapped exception
alt Is AccessDeniedException?
Transformer->>Transformer: Map to forbidden()
else Is ApiProblemException?
Transformer->>Transformer: Transform accordingly
else Other
Transformer->>Transformer: Generic error handling
end
Transformer->>Response: Generate ApiProblem response
Response->>Client: Return HTTP response
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
Summary by CodeRabbit
Release Notes
Bug Fixes
Tests