Closed babebridou closed 7 years ago
fixed with following update @tabkram: why do we need to keep track of selectedItem in self ?
--
delete self.selectedElementId;
delete self.selectedItem;
} else {
console.log("select a node:");
}
}
The bug now also occurs when you create a scenario, click on repository, click back on scenarios, and click on add a new scenario.
angular.js:12798 TypeError: Cannot read property '$parent' of undefined
at Object.getParentId (webix_debug.js:12574)
at Object.getParentId (webix_debug.js:10582)
at tree.layout.service.js:109
at Object.webix.ready (webix_debug.js:910)
at Object.saveConcernedNode (tree.layout.service.js:103)
at Scope.$scope.addNodeToParent (scenario.controller.js:95)
at fn (eval at compile (angular.js:13643), <anonymous>:4:253)
at expensiveCheckFn (angular.js:14625)
at callback (angular.js:24093)
at Scope.$eval (angular.js:16374)
106_delete_it merged to master, other issues found for folder (tracked through issue #118)
issue #118 fixed and merged in master
deleting a scenario leads to an unstable situation: the selected node in the tree no longer exists and an angular exception is raised when the user tries to create a new scenario.
Some node deletions also fail with "Error: has child nodes!" even when they don't.