rowRenderer onclick

[cheton]

rowRenderer onclick

[cheton]

A click event will call row renderer twice, this is the expected behavior. The first call is to render the next selected node, the second call is to render previous selected node so it will display the unselected state:

// Select this node
if (this.state.selectedNode !== node) {
    node.state.selected = true;

    // Update the row corresponding to the node
    this.rows[nodeIndex] = this.options.rowRenderer(node, this.options);
}

// Deselect the current node
if (this.state.selectedNode) {
    const selectedNode = this.state.selectedNode;
    const selectedIndex = this.nodes.indexOf(this.state.selectedNode);
    selectedNode.state.selected = false;
    this.rows[selectedIndex] = this.options.rowRenderer(selectedNode, this.options);
}

In your case, the updateNode method does not remove unused id from the lookup table (e.g. this.nodeTable) because I didn't expect one would ever change the node id. I think that would be the problem that caused an error.

Lets take a look at getNodeById, it will lookup the node by id from the nodeTable, if an unused node id was not removed from the nodeTable, it will return the node immediately, and therefore caused unexpected behavior.

 getNodeById(id) {
    let node = this.nodeTable.get(id);
    if (!node) {
        // Find the first node that matches the id
        node = this.nodes.filter((node) => {
            return (node.id === id);
        })[0];
        if (!node) {
            return null;
        }
        this.nodeTable.set(node.id, node);
    }
    return node;
}

[cheton]

The lookup table should be refreshed when changing the node id with updateNode. I will fix it in the next release.

[cheton]

Fixed in v1.8.2