From 50711e960021a298acb980ef45fbb705d23d2661 Mon Sep 17 00:00:00 2001
From: Nakul Nagargade <nakul@tooljet.com>
Date: Wed, 12 Mar 2025 11:26:05 +0530
Subject: [PATCH] Fix visibility and disable variables naming conventions

---
 frontend/src/Editor/Components/TextInput.jsx | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/frontend/src/Editor/Components/TextInput.jsx b/frontend/src/Editor/Components/TextInput.jsx
index 29fbaaa625..ce482947a9 100644
--- a/frontend/src/Editor/Components/TextInput.jsx
+++ b/frontend/src/Editor/Components/TextInput.jsx
@@ -236,8 +236,6 @@ export const TextInput = function TextInput({
       value: properties.value,
       isMandatory: isMandatory,
       isLoading: loading,
-      isVisible: visibility,
-      isDisabled: disable,
     };
 
     setExposedVariables(exposedVariables);
@@ -245,6 +243,17 @@ export const TextInput = function TextInput({
     // eslint-disable-next-line react-hooks/exhaustive-deps
   }, []);
 
+  useEffect(() => {
+    // Fix for "visibility is not defined" in production because there's a naming conflict in the code.
+    // The issue is in the exposedVariables object where we had both a function named visibility and a property isVisible that depends on the state variable with the same name.
+    const exposedVariables = {
+      isVisible: visibility,
+      isDisabled: disable,
+    };
+    setExposedVariables(exposedVariables);
+    // eslint-disable-next-line react-hooks/exhaustive-deps
+  }, []);
+
   const setInputValue = (value) => {
     setValue(value);
     setExposedVariable('value', value);