Closed calvinmetcalf closed 10 years ago
nope not a problem with enumerablilty
but more generally looks like it's breaking the ability to structured clone something.
though it does not break web workers from what I can tell, I don't know if structured cloning is implemented the same way for both
FWIW, I've used EmberJS with raw IndexedDB without an issue. See this pretty old gist: https://gist.github.com/leepfrog/5352059
you are calling record.serialize on your objects before putting them into indexDB, that's all well and good for an ember app but doesn't deal with the fact that everything else using indexedDB is broken by ember being on the page.
@stefanpenner any ideas on this one?
@knownasilya haven't had a chance to look into this yet. I'll try to find some time this weekend. Busy with client work right now.
Closing due to inactivity. If this is still an issue, please let me know and I'll reopen.
@calvinmetcalf is this still causing you guys issues?
We changed to a different method of cloning objects and the problem went away, no idea about the root issue. On Nov 1, 2014 3:54 PM, "Stefan Penner" notifications@github.com wrote:
@calvinmetcalf https://github.com/calvinmetcalf is this still causing you guys issues?
— Reply to this email directly or view it on GitHub https://github.com/emberjs/ember.js/issues/4832#issuecomment-61380915.
yay
try to put an object into indexedDB with PouchDB, if the object has an array in it, then you get an error, don't load ember or set
ENV.EXTEND_PROTOTYPES = false
and it goes in fine, my first guess would be that not all of the things added to the array prototype are properly set non-enumerable.The error in question is:
js bin to reproduce it http://jsbin.com/vicofito/2/edit
see pouchdb/pouchdb#2158