Update file-tidy extension - #30294
Conversation
- New extension icon, with all three Store screenshots re-shot to match - Fix: previewing a plan no longer writes the perceptual-hash cache (or creates the destination folder) before the user confirms; the cache is written after a successful run, keyed by each image's final archived path
|
Thank you for the update! 🎉 We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days. |
Greptile SummaryThe PR refreshes File Tidy's icon and Store screenshots and moves perceptual-hash persistence from preview analysis to completed execution.
Confidence Score: 5/5The PR appears safe to merge because no blocking failure remains. No blocking failure remains. Important Files Changed
Reviews (3): Last reviewed commit: "Update CHANGELOG.md and optimise images" | Re-trigger Greptile |
Addresses review feedback on the deferred hash-cache write: cross-volume moves now preserve the source mtime so re-keyed cache entries stay valid, and saving the cache merges with the on-disk state instead of overwriting entries a concurrent run wrote.
|
Both cache-related review comments verified and addressed in be8ac13:
Both are covered by new tests (cross-volume move keeps mtime and the entry still hits; merge keeps another run's entries while dead paths drop). |
|
Published to the Raycast Store: |
|
🎉 🎉 🎉 We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag. |
Description
Two changes for File Tidy:
ray lintmetadata checks pass)..tidyfolder inside it) just for previewing a plan — and silently skipped the "create destination?" consent prompt. The cache is now written only after a run completes, keyed by each image's final archived path so later runs still get cache hits. Covered by two new regression tests in the shared core (60/60 passing).Screencast
Updated screenshots are included in
metadata/(form, plan top, plan bottom).Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare located outside the metadata folder if they were not generated with our metadata tool