can't get Backbone.dualStorage working with requireJS about backbone.dualstorage HOT 10 CLOSED

while debugging it appears that "Store.prototype.create" function line 165 doesn't receive backbone models but the whole xhr response object like : { request : Object , success : Object }

from backbone.dualstorage.

the undefined 'set' error is probably because your server returns something other than 'id' as the 'id' attribute - eg 'ID' or '_id'. Either change the server response or parse the incoming data using parse or parseBeforeLocalSave methods on your collection/model. That error also indicates the requireJS is loading things in the right order.

from backbone.dualstorage.

i've juste taken a look and my server is returning the "id" attribute correctly ...

from backbone.dualstorage.

But i still don't get a clue why the whole xhr response is passed to the Store.prototype.create method instead of this method being served model by model...

from backbone.dualstorage.

There is a known issue where Store.create is sometimes passed a backbone model and sometimes passed its attributes. I'll be working on this next when I find some time. See the comments in #37.

from backbone.dualstorage.

Ok cool, I finally made it work on few collections. Actually , i didn't really understand since now the use of parseBeforeLocalSave, and it happened that the response was not parsed at all while entering the dualStorage process, thus, not passing response.response, but the whole response object. So my collections are well parsed now, but i'm still facing couple of issues, i'll let you know after some work ...

from backbone.dualstorage.

Oh yeah , i made it work finally , thanks for the answers !

By the way i have another question : how do you manage memory use when the application's cache is reaching the maximum size ( around 5Mo i think ) ? Are you deleting the oldest model ? is it possible to customise this function ? The backbone-fetch-cache is doing the job for that
https://github.com/mrappleton/backbone-fetch-cache#priorityfn

from backbone.dualstorage.

I'm glad you got it working.

That's actually a big problem that we are hoping someday to resolve using a storage backends like IndexedDB which can grow beyond the 5mb (FireFox) or 2.5mb (Chrome) that is allotted to localstorage. My plan is to use Lawnchair as a common interface to both localstorage and IndexedDB. Before that can happen, we're going to have to stop relying on Store being synchronous as it is now with localstorage. IndexedDB and Lawnchair give all responses as asynchronous callbacks. This could happen either by making everything use callbacks internally, or using something like promises.

Unfortunately, I'm not going to be able to implement that anytime soon. There are more pressing issues, and my time is limited. Let me know if this is something you'd be interested in working on though.

from backbone.dualstorage.

@matthieugayon Can you please provide some details about how you got it to work? I am having the same issue, it seems.

from backbone.dualstorage.

There were a couple problems mentioned here. What problem specifically are
you having?

On Friday, September 27, 2013, BananaNeil wrote:

@matthieugayon https://github.com/matthieugayon Can you please provide
some details about how you got it to work? I am having the same issue, it
seems.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/46#issuecomment-25283703
.

from backbone.dualstorage.