feat(desktop): support native launchers cross-platform - #179
Conversation
|
Warning Review limit reached
Next review available in: 4 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
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 |
What changed
Open in…launcher on every Tauri desktop platform; macOS keeps the overlay band while Windows and Linux render below native window chrome..desktopentries,TryExec, XDG application directories, and hicolor-compatible icon lookup, including selected file-manager and terminal launch behavior.Why
PR #178 introduced native installed-app discovery for macOS. Windows and Linux still used the browser fallback and returned no native applications. This brings the same task context and installed-application launcher experience to all supported desktop targets while following each OS's registration model instead of guessing from a shared PATH.
Validation
pnpm --dir web test— 19 tests passedmake lint-webmake build-webgo test ./...cargo test --manifest-path desktop/src-tauri/Cargo.toml— 3 macOS tests passedcargo clippy --manifest-path desktop/src-tauri/Cargo.toml --all-targets -- -D warningscargo clippy --target x86_64-pc-windows-msvc --all-targets -- -D warningswith Tauri bundle resources disabled for cross-checkingx86_64-unknown-linux-gnutarget check passed, and Clippy passed in an isolated harnessgit diff --checkmake lintremains blocked by the existing 44SA5011findings in untouched Go test files. The complete Tauri Linux cross-build additionally requires a Linux GTK/GDK sysroot, which is not installed on the macOS development host; the Linux platform module itself was target-compiled and tested independently.