From 6eebd10dc105ee9e25d3661bfd553dc2aae23ce7 Mon Sep 17 00:00:00 2001
From: TekH <h.tek@digitaldata.works>
Date: Wed, 3 Dec 2025 13:43:39 +0100
Subject: [PATCH] Add DELETE endpoint to RecActionController for testing

A new HTTP DELETE endpoint has been added to the
`RecActionController` class, accessible via the `"fake"` route.
The `Delete` method is asynchronous and uses the `mediator.Send`
method to execute a `DeleteRecActionsCommand` with a hardcoded
`ProfileId` value of `2`. The method returns an HTTP 204 No
Content response. This endpoint appears to be intended for
testing or placeholder purposes.
---
 src/ReC.API/Controllers/RecActionController.cs | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/ReC.API/Controllers/RecActionController.cs b/src/ReC.API/Controllers/RecActionController.cs
index 402867f..f47f7be 100644
--- a/src/ReC.API/Controllers/RecActionController.cs
+++ b/src/ReC.API/Controllers/RecActionController.cs
@@ -71,5 +71,16 @@ public class RecActionController(IMediator mediator) : ControllerBase
 
         return NoContent();
     }
+
+    [HttpDelete("fake")]
+    public async Task<IActionResult> Delete(CancellationToken cancel)
+    {
+        await mediator.Send(new DeleteRecActionsCommand()
+        {
+            ProfileId = 2
+        }, cancel);
+
+        return NoContent();
+    }
     #endregion CRUD
 }
\ No newline at end of file