Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe change makes Windows Explorer reveal launches wait for helper completion, capture stderr, validate target paths in PowerShell, and return detailed errors. Tests cover failed helpers, missing targets, missing launchers, and valid temporary files. ChangesExplorer reveal error handling
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Severity of issue fixed: Medium Sequence Diagram(s)sequenceDiagram
participant fileExplorerRevealLaunch
participant launchEditorProcess
participant PowerShell
fileExplorerRevealLaunch->>launchEditorProcess: set waitForExit
launchEditorProcess->>PowerShell: spawn reveal helper with piped stderr
PowerShell->>PowerShell: validate target with Test-Path
PowerShell-->>launchEditorProcess: return exit code and stderr
launchEditorProcess-->>fileExplorerRevealLaunch: return success or ExternalLauncherEditorSpawnError
Suggested reviewers: Merge Risk: ⚪ Minimal · up to Windows reveal failures are handled with actionable errors and focused coverage. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Windows Reveal in File Explorer returns success as soon as PowerShell starts, hiding later launch failures from the existing error toast. Capturing those failures also exposes PowerShell's raw CLIXML output. This change makes those errors detectable and readable: wait for the short-lived helper, check its exit status, reject missing targets, and return the exception message as plain text while preserving Explorer's selection quoting.
Fixes #11172, which tracks error reporting. The originally reported Explorer no-op was not reproduced, and this PR does not claim to diagnose or fix its unknown cause.
Validation:
Path does not exist: ...text for a missing file. Native Electron context-menu interaction was not independently verified.Implemented by GPT-6 using Codex.