Angular's Debug Data must be enabled for scope and isolateScope to work

[mike-ward]

The watcher for expandedNodes relies on $liElment.scope() (line 239) to return a valid value. When Angular's Debug Data is disabled (typical for production), this method returns null. This generates an exception. It also disables tree-control from responding to changes in expandedNodes.

See issue: angular/angular.js#9515

[ghost]

Please fix this, it's a horribly bad bug. Or explain the logic behind why it cant be fixed

[alphilo]

Please fix this as enable debug cause the performance issue.

[yoavaa]

I am not sure how to fix this as the tree control relays on getting the scope.$id
Is there any other way to get the id of a scope without accessing the scope() method?

[benavern]

Has somebody found something working to fix this error ??? I'm experiencing the same error...
Error: existingScope is undefined
when debug mode is off...
thank's in advance to those who will answere :)

[yoavaa]

Guys, there is no fix to this problem save to rewrite the tree control to
use a different method of identifying nodes.
This is a big change and a breaking change, so I am not that fast to make
it.

On Mon, Mar 23, 2015 at 10:33 AM, Benjamin CARADEUC <
[email protected]> wrote:

Has somebody found something working to fix this error ??? I'm
experiencing the same error...
Error: existingScope is undefined
when debug mode is off...
thank's in advance to those who will answere :)

—
Reply to this email directly or view it on GitHub
#101 (comment)
.

[szabyg]

+1

[ftorghele]

+1

[tmarkley]

Has anyone been able to solve this?

[rmsint]

Just read about using a cloned _scope here https://github.com/a5hik/ng-sortable/pull/156/files. Maybe more a workaround, however it could prevent a rewrite and fix the error when disabling debug.

[yoavaa]

made a similar solution - hope it will be sufficient.