fix: bug when deleting sibling elements

[Grafikart]

Since deletions is controlled by "commitDeletion" , commitWork should not be triggered further in the fiber tree for old fibers.

[Grafikart]

This is an example of code that crashes without this PR

  function Counter () {
    const [n, increment] = useIncrement()
    return (
      <p id="b">
        Count: {n}
        <button onClick={increment}>Incrémenter</button>
      </p>
    )
  }

  function move () {
    const container = document.getElementById('root')
    Didact.render(<div>Hello</div>, container)
  }

  const element = <div id="a">
    <h1>Mon compteur</h1>
    <Counter />
    <button onClick={() => move()}>Move</button>
  </div>

  Didact.render(element, container)

[sschottler]

Since deletions is controlled by "deletions" , commitWork should not be triggered further in the fiber tree for old fibers.

This fixed my issue! I think you meant to say "deletions are controlled by commitDeletion"

[Grafikart]

Yeah I meant commitDeletion sorry, I fixed my original message.

[sschottler]

Also seems to fix #19

[zbzalex]

} else if (vnode.effectTag === "DELETION") { commitDeletion(vnode, domParent) return }