-
-
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
regression 3.0: ArrayProxy#pushObjects doesn't accept ArrayProxy #16621
Comments
@rwjblue Nope, this seems good. It would also be useful if we could mark all the methods that are derived from |
using |
@runspired - Yes, that would work right, but I believe that it muddies the waters a bit more than the proposed fix... |
I have same problem I can't use |
@devdemi you can get around the issue currently by called
|
#16131 cleaned up a lot of
Enumerable
andArray
mixin code.However it also changed the assertion in
pushObjects
from checking for Enumerable or Array to only checking ArrayThis assertion now throws when calling
hasMany.pushObjects(otherHasManyOrRecordArray)
even though ember-data'sManyArray
can accept these objects.After going over this with @rwjblue I think the path forward is
pushObjects
entirelyreplace
(which is the method implementations ofMutableArray
are expected to implement)NativeArray
already does assert inreplace
andArrayProxy
doesn't need to as it delegates tocontent
.The text was updated successfully, but these errors were encountered: