Hooks now will not create new snapshots while time jumping

Author: davidchai717

package/linkFiber.js

@@ -45,11 +45,8 @@ module.exports = (snap, mode) => {
 
   function changeUseState (component) {
     if (component.queue.dispatch.linkFiberChanged) return;
-    // running the original useState and storing its result (state and dispatch function)
-    const oldDispatch = component.queue.dispatch.bind(component.queue);
     // storing the original dispatch function definition somewhere
-    console.log('inside changeusestate', oldDispatch);
-
+    const oldDispatch = component.queue.dispatch.bind(component.queue);
     // redefining the dispatch function so we can inject our code
     component.queue.dispatch = function (fiber, queue, action) {
       console.log('mode', mode);
@@ -102,6 +99,7 @@ module.exports = (snap, mode) => {
     // TODO: Refactor the conditionals - think about the edge case where a stateful
     // component might have a key called 'baseState' in the state
     if (memoizedState && memoizedState.hasOwnProperty('baseState')) {
+      console.log("I'm not supposed to run", currentFiber);
       memoizedState.traversed = traverseHooks(memoizedState);
       nextTree = tree.appendChild(memoizedState);
     }
@@ -115,6 +113,7 @@ module.exports = (snap, mode) => {
 
   function updateSnapShotTree() {
     const { current } = fiberRoot;
+    console.log('current', current);
     snap.tree = createTree(current);
   }
 
@@ -132,41 +131,5 @@ module.exports = (snap, mode) => {
         if (action === 'contentScriptStarted') sendSnapshot();
       });
     },
-    // testHooks(react) {
-    //   return {
-    //     useState: initialState => {
-    //       // running the original useState and storing its result (state and dispatch function)
-    //       const toReturn = react.useState(initialState);
-    //       // storing the original dispatch function definition somewhere
-    //       const oldDispatch = toReturn[1];
-    //       console.log('old dispatch', oldDispatch)
-    //       // redefining the dispatch function so we can inject our code
-    //       toReturn[1] = function (newVal) {
-    //         oldDispatch(newVal);
-    //         setTimeout(() => {
-    //           updateSnapShotTree();
-    //           sendSnapshot();
-    //         }, 100);
-    //       };
-    //       return toReturn;
-    //     },
-    //     useReducer: (reducer, initialState, init) => {
-    //       // Declare a constant and initialize to the built-in useReducer method
-    //       // Which returns an array with the state and dispatch
-    //       const reduced = react.useReducer(reducer, initialState, init);
-    //       // Save the dispatch method
-    //       const oldDispatch = reduced[1];
-    //       // reassign the dispatch method with the additional methods
-    //       reduced[1] = function (type) {
-    //         oldDispatch(type);
-    //         setTimeout(() => {
-    //           updateSnapShotTree();
-    //           sendSnapshot();
-    //         }, 100);
-    //       };
-    //       return reduced;
-    //     },
-    //   };
-    // },
   };
 };

package/timeJump.js

@@ -12,8 +12,6 @@ module.exports = (origin, mode) => {
   // recursively change state of tree
   function jump(target, coords = []) {
     const originNode = traverseTree(origin.tree, coords);
-    console.log('coords', coords);
-    console.log('originNode', originNode);
     // set the state of the origin tree if the component is stateful
     if (originNode.component.setState) {
       originNode.component.setState(target.state, () => {
@@ -44,6 +42,8 @@ module.exports = (origin, mode) => {
     // setting mode disables setState from posting messages to window
     mode.jumping = true;
     jump(target);
-    mode.jumping = false;
+    setTimeout(() => {
+      mode.jumping = false;
+    }, 100);
   };
 };