Fixed a reset/state bug in useEditableValue() hook and removed unnecessary useMemo()

Author: Brian Vaughn

packages/react-devtools-shared/src/devtools/views/hooks.js

@@ -12,7 +12,6 @@ import {
   useCallback,
   useEffect,
   useLayoutEffect,
-  useMemo,
   useState,
 } from 'react';
 import {unstable_batchedUpdates as batchedUpdates} from 'react-dom';
@@ -42,11 +41,14 @@ export function useEditableValue(
   const [parsedValue, setParsedValue] = useState(initialValue);
   const [isValid, setIsValid] = useState(initialIsValid);
 
-  const reset = useCallback(() => {
-    setEditableValue(smartStringify(initialValue));
-    setParsedValue(initialValue);
-    setIsValid(initialIsValid);
-  }, []);
+  const reset = useCallback(
+    () => {
+      setEditableValue(smartStringify(initialValue));
+      setParsedValue(initialValue);
+      setIsValid(initialIsValid);
+    },
+    [initialValue, initialIsValid],
+  );
 
   const update = useCallback(newValue => {
     let isNewValueValid = false;
@@ -65,17 +67,14 @@ export function useEditableValue(
     });
   }, []);
 
-  return useMemo(
-    () => ({
-      editableValue,
-      hasPendingChanges: smartStringify(initialValue) !== editableValue,
-      isValid,
-      parsedValue,
-      reset,
-      update,
-    }),
-    [editableValue, initialValue, isValid, parsedValue],
-  );
+  return {
+    editableValue,
+    hasPendingChanges: smartStringify(initialValue) !== editableValue,
+    isValid,
+    parsedValue,
+    reset,
+    update,
+  };
 }
 
 export function useIsOverflowing(