Add per-instance Seeker settings#565
Conversation
|
@sourcery-ai review |
|
@greptileai review |
Greptile SummaryThis PR moves Confidence Score: 5/5Safe to merge — all remaining findings are P2 style/quality suggestions with no correctness impact on the happy path. The two previously flagged P1 issues (enabled-check inconsistency in BackgroundJobManager and the controller's previousAnyUseCustomFormatScore snapshot) are both resolved. The migration is correct and reversible. The only remaining findings are: missing server-side bounds validation on per-instance fields (bypassable only via direct API, not through the UI), Moq still used in existing test files being modified, and a minor frontend validation gap. None of these affect runtime correctness for normal use. code/backend/Cleanuparr.Api/Features/Seeker/Contracts/Requests/UpdateSeekerInstanceConfigRequest.cs — no server-side validation on MinCycleTimeDays / ActiveDownloadLimit bounds. Important Files Changed
Reviews (2): Last reviewed commit: "fixed enabled checks" | Re-trigger Greptile |
|
@greptileai review |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
Relates to #536