fix: onNodesChange now updates its state correctly

[akucinskii]

There is a problem with onNodesChange using state from the initialization of component

This fixes it at now it updates the value correctly:

Old code example:

 console.log(mode) //1st call: firstMode, 2nd call: secondMode
  return (
    <Editor
      enabled={true}
      onNodesChange={(query) => {
        console.log(mode); //1st call: firstMode, 2nd call: firstMode (always firstMode no matter what)
      
      }}
      resolver={{ ... }}
    >
      {children}
    </Editor>
  );

New code example:

 console.log(mode) //1st call: firstMode, 2nd call: secondMode
  return (
    <Editor
      enabled={true}
      onNodesChange={(query) => {
        console.log(mode); //1st call: firstMode, 2nd call: secondMode
      
      }}
      resolver={{ ... }}
    >
      {children}
    </Editor>
  );

Screenshot of working example:

Code of this example screenshot:

const [count, setCount] = useState(0);

 return (
   <>
     <Editor
       resolver={{
         Item: Item,
         Toolbox: Toolbox,
       }}
       onNodesChange={() => {
         console.log('nodes changed, current count state: ', count);
       }}
     >
...

[Savuelo]

Same issue here please fix