feat: warn in the compile response when the compile stops an active Play session - #2372
Conversation
Compile already warned when pause points were active, but Play-only compiles returned no Warning even though the session was discarded. Keep the existing pause-point wording unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (14)
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe compile flow now builds a Play Mode stop warning before validation. The warning uses captured Play Mode state, propagates through compilation and response creation, and remains available in immediate and stored responses. Tests cover warning branches and persistence paths. ChangesCompile warning flow
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: ⚪ Minimal · up to The compile response now warns when compiling stops an active Play session and discards its state; no actionable merge-blocking risk remains after normal checks and review. Sequence Diagram(s)sequenceDiagram
participant CompileUseCase
participant CompilationExecutionService
participant CompileController
participant CompileResponseFactory
participant CompileSessionResultStore
CompileUseCase->>CompileUseCase: Capture Play Mode state and pause-point count
CompileUseCase->>CompileResponseFactory: Build response with playModeStopWarning
CompileUseCase->>CompilationExecutionService: Execute compilation with warning
CompilationExecutionService->>CompileController: TryCompileAsync with warning
CompileController->>CompileResponseFactory: Record result with warning
CompileResponseFactory->>CompileSessionResultStore: Store compile response
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 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 |
A compile that actually discarded Play Mode still returned no Warning when state validation failed or external Scene changes aborted before compile. Rename the warning identifiers to match that broader Play-stop meaning. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
uloop compilenow warns when the request arrives during Play Mode, even if no pause points are enabled.User Impact
Changes
Verification
CompilePausePointWarningBuilderTests— TestCount 3, PassedCount 2, FailedCount 1. The new Play-without-pause-points case expected the new literal and receivednull.dist/darwin-arm64/uloop compile— Success true, ErrorCount 0.CompilePlayModeStopWarningBuilderTests— TestCount 3, PassedCount 3, FailedCount 0.dist/darwin-arm64/uloop run-tests(single run) — TestCount 3392, PassedCount 3384, FailedCount 0, SkippedCount 8. Suite Status wasSkipped/ Success false because of those skips; there were no failures.