[L-06] Add a graceful Usage Dock quit request - #621
Arrangedgodly wants to merge 1 commit into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe desktop process now recognizes ChangesLaunchpad quit handling
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to The Launchpad quit flag exits an existing Usage Dock instance or prevents a new invocation from completing startup. No actionable merge risk remains; the change is ready for normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 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 |
Behavior
Usage Dock recognizes the exact sole argument --quit-from-launchpad. If an instance is already open, the single-instance callback exits it. If no instance is open, the flagged invocation exits during setup before tray services start. This gives Launchpad a local graceful quit path without adding an HTTP shutdown endpoint.
Verification
The installed app needs a build containing this change. A Windows app session was not launched for runtime testing.
Summary by CodeRabbit