-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError for Ember.computed.sort in DependentArraysObserver.prototype.dependentArrayWillChange #5596
Labels
Comments
@rhyek can you check this in 1.8? |
Just updated that jsbin to ember 1.8.0 and ember-data 1 beta 11. Still has the same issue. |
Merging into #9462 |
5 tasks
stefanpenner
added a commit
to stefanpenner/ember.js
that referenced
this issue
Jun 26, 2015
…rjs#9462, emberjs#4919, emberjs#4231, emberjs#3706, emberjs#5596, emberjs#9485, emberjs#9492, emberjs#5319, emberjs#5268, emberjs#4831, emberjs#5558] Move away from AC/RC instead use the simpler naive enumerable methods, and rely on glimmers stable rendering for efficiency. For more complex scenarios, custom solutions should be used. @wagenet & @stefanpenner
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using Ember 1.7 and having an issue with DependentArraysObserver.prototype.dependentArrayWillChange at line 25860 (http://builds.emberjs.com/tags/v1.7.0/ember.js) where a TypeError is raised because observerContexts[sliceIndex] is undefined:
I have a jsbin here. (click on 'clear'). The problem only seems to occur in the specific case where i have both sortableTable views up (even though they're independent of each other) and at least the second has it's Ember.computed.sort computed property's sortProperties set to a non-empty array.
I've noticed that just before the exception is raised, at line 25815 when this line is called inside trackRemove:
trackedArray is undefined while dependentArray still points to my underlying data.
In any case, changing this:
to this:
solves my problem.
The text was updated successfully, but these errors were encountered: