fix: open original file using plugin-opener instead of deprecated plugin-shell - #1507
fix: open original file using plugin-opener instead of deprecated plugin-shell#1507JIturiDashami wants to merge 1 commit into
Conversation
|
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 selected for processing (3)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe media panel now opens the current image path with Tauri’s opener plugin. The capability configuration grants scoped access to all paths. Tests mock ChangesOpen Original File
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR updates opening original files to use the supported plugin path and preserves access for user-selected image locations; no actionable merge-blocking risk remains after normal checks and review. Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4✅ 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 |
Link your account with GitcordThanks for opening this PR, @JIturiDashami! To receive Discord notifications and contributor tracking for this organization:
Once linked, Gitcord can notify you about reviews, merges, and more. — Posted by Gitcord |
…gin-shell (#1165)
Addressed Issues:
Fixes #1165
Screenshots/Recordings:
Additional Notes:
Before: Clicking "Open Original File" did nothing , button was silently disabled
After: Clicking "Open Original File" now opens the image in the default Windows Photos viewer.
AI Usage Disclosure:
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact. AI slop is strongly discouraged and may lead to banning and blocking. Do not spam our repos with AI slop.
Check one of the checkboxes below:
I have used the following AI models and tools: Claude (Anthropic) — used to analyze the root cause and help write the fix and tests. I reviewed and tested everything myself, including end-to-end in the running app.
Checklist
Summary by CodeRabbit