From f4abac1103b43bc71918b95aeef5e9270a4cd6ae Mon Sep 17 00:00:00 2001
From: Developer 02 <developer02@didaloghe.onmicrosoft.com>
Date: Fri, 5 Dec 2025 23:39:22 +0100
Subject: [PATCH] Mark InvokeRecAction as obsolete with guidance

Added the `[Obsolete]` attribute to the `InvokeRecAction` method
in the `ReC.Client` namespace to discourage its use. The attribute
recommends using the `InvokeRecActionAsync` method instead to
avoid potential deadlocks and improve performance.
---
 src/ReC.Client/ReCClient.cs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/ReC.Client/ReCClient.cs b/src/ReC.Client/ReCClient.cs
index 758b2f8..4e4bcb8 100644
--- a/src/ReC.Client/ReCClient.cs
+++ b/src/ReC.Client/ReCClient.cs
@@ -36,6 +36,7 @@ namespace ReC.Client
         /// </summary>
         /// <param name="profileId"></param>
         /// <returns>True if the request was successful, false otherwise</returns>
+        [Obsolete("Use InvokeRecActionAsync instead to avoid potential deadlocks and improve performance.")]
         public bool InvokeRecAction(int profileId)
         {
             var resp = _http.PostAsync($"api/RecAction/invoke/{profileId}", content: null).GetAwaiter().GetResult();