src/Ombi/Controllers/V1/IssuesController.cs (1)

309-314: Prefer batched comment deletion to avoid N database writes.

Line 310–313 currently performs one delete/save per comment. Use DeleteRange to reduce round-trips and tighten the deletion path.

💡 Suggested change

-            var comments = await _issueComments.GetAll().Where(x => x.IssuesId == id).ToListAsync();
-            foreach (var comment in comments)
-            {
-                await _issueComments.Delete(comment);
-            }
+            var comments = await _issueComments.GetAll().Where(x => x.IssuesId == id).ToListAsync();
+            if (comments.Count > 0)
+            {
+                await _issueComments.DeleteRange(comments);
+            }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/Ombi/Controllers/V1/IssuesController.cs` around lines 309 - 314, The
current loop fetches comments via _issueComments.GetAll().Where(x => x.IssuesId
== id).ToListAsync() and deletes them one-by-one using
_issueComments.Delete(comment), causing N database writes; replace the
per-comment deletes with a single batched call (e.g.,
_issueComments.DeleteRange(comments) or an equivalent repository method) so the
controller uses one delete/save operation for the entire collection and removes
the foreach that calls Delete for each comment.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes