Fixed the regression in addChildNodes

[acierto]

Hey,
I found one more regression introduced in v0.14.*

Currently the issue in the addChildNodes.
If you call addChildNodes it will append children and open them immediately, regardless of the status of the parent node, was it opened or not.

That leads to a broken state of the tree. Those nodes which user see are not usable anymore, and when you click on parent toggler these nodes will be duplicated and you can operate only with them.

[coveralls]

Coverage increased (+0.01%) to 82.218% when pulling b429ade on acierto:master into ca7829d on cheton:master.

[coveralls]

Coverage remained the same at 82.207% when pulling 2087602 on acierto:master into ca7829d on cheton:master.

[cheton]

The "if" statement should handle only this.nodes and this.rows, so the parent node will have chance to update content after adding new child nodes. For example, assume that there is a label aside the parent node, showing a total number of its descendant child nodes.

if (parentOffset >= 0) {
    if (parentNode.state.open === true) {
        // Update nodes & rows
        this.nodes.splice.apply(this.nodes, [parentOffset + 1, deleteCount].concat(nodes));
        this.rows.splice.apply(this.rows, [parentOffset + 1, deleteCount].concat(rows));
    }

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

[acierto]

Yes you are right, applied a feedback!

[acierto]

Would be it possible to release a new version today based on this fix?
As we have a release tomorrow, a bit critical for us.

[cheton]

Sure! I will publish a new release soon.

[cheton]

Published v1.14.7