Repository navigation
chore: Move compile disconnect policy into Domain - #1537
Conversation
Keep transport parsing in infrastructure while centralizing the compile-specific cancellation decision in a pure domain policy.
|
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 (2)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughIntroduces a new ChangesCompile Cancellation Policy Extraction
Estimated code review effort: 2 (Simple) | ~12 minutes Sequence Diagram(s)sequenceDiagram
participant Client
participant JsonRpcProcessor
participant JsonRpcAcceptedRequestCancellationPolicy
Client->>JsonRpcProcessor: ProcessRequestWithEarlyResponseAsync(compile request)
JsonRpcProcessor->>JsonRpcProcessor: ReadCompileRequestWaitsForDomainReload(params)
JsonRpcProcessor->>JsonRpcAcceptedRequestCancellationPolicy: ShouldCancelOnClientDisconnect(method, compileWaitsForDomainReload)
alt method not compile
JsonRpcAcceptedRequestCancellationPolicy-->>JsonRpcProcessor: true
else compileWaitsForDomainReload is null or true
JsonRpcAcceptedRequestCancellationPolicy-->>JsonRpcProcessor: false
else compileWaitsForDomainReload is false
JsonRpcAcceptedRequestCancellationPolicy-->>JsonRpcProcessor: true
end
JsonRpcProcessor-->>Client: accepted result with cancelOnClientDisconnect
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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
User Impact
Changes
Verification