Post-completion job actions #10
Loading…
Reference in a new issue
No description provided.
Delete branch "d/post-job-action"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Each job can now run an action when it finishes: move the output to a chosen folder (never overwrites, suffixes instead, and the job record follows the file) or show it in Explorer. Configured via a dropdown on the stepper source step with a folder picker and a pre-flight check.
🤖 Claude AI Code Review
Summary: Adds a post-completion action per job (move output with non-overwriting suffixing, or reveal in Explorer), wired through the model, DB schema check, stepper UI, and queue service.
Code Quality ⭐⭐⭐⭐☆
Clean, well-scoped change with sensible best-effort error handling and a non-overwriting move strategy.
Issues
🟡 RenderQueueService.cs —
explorer.exeand the/select,argument are Windows-only. If the app is meant to run on Avalonia/desktop cross-platform, this silently fails (caught) on macOS/Linux. Consider platform-guarding or using the appropriate reveal mechanism per OS.🟡 DatabaseInitializationService.cs — The schema check now selects
PostAction, PostActionTarget, but the diff shows no migration adding those columns. If there's no automatic migration/recreation path, existing databases will fail the schema check on upgrade. Confirm the outdated-schema branch actually recreates/migrates the table.🟢 RenderQueueService.cs —
File.Moveacross volumes will throw if source and destination are on different drives (copy+delete needed). This is caught and logged, but the move silently won't happen. ConsiderFile.Move(src, dst, overwrite:false)semantics still don't cross-volume-copy; a fallback copy may be desired.📊 Tokens: 4782 input + 575 output | 💰 Cost: ~$0.0383
Generated by Claude Opus 4.8 via Gitea Actions