fix: Settings no longer shows the CLI as installed after uninstall#1154
Conversation
Remove the stale C# uninstall path that deleted the native CLI binary directly. Settings now delegates uninstall to the installed launcher and waits until the deferred self-removal has finished before refreshing CLI status, avoiding a stale installed display after Windows uninstall.
📝 WalkthroughWalkthroughThe pull request refactors the native CLI installer's uninstall flow from synchronous legacy PATH-removal helpers to an asynchronous polling mechanism. ChangesAsync uninstall target removal
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
Replace personal-looking usernames in path fixtures with ExampleUser placeholders so installer and CLI tests keep their platform coverage without embedding local developer names.
Replace product-like project names in path fixtures with generic sample project names so the tests do not embed local or customer-looking project identifiers.
Summary
User Impact
CLI: v3.0.0-beta.9even afteruloop -vno longer resolved in the terminal.Changes