Michiel de Jong

@skddc do you want to pair on this now?

http://remotestorage.io/coverage/lcov-report/src/index.html

leaving this one for next month

IIRC, the problem with this is that in our IndexedDB database, the metadata is stored on the item, not on the containing folder node. So if you do getListing on...

when get requests are not getting resolved, it affects library behavior quite badly - you would for instance do: ``` js remoteStorage.scope('/myfavoritedrinks/').getObject('aervoqirjvsergergs', 0) .then(function(obj) { console.log('get request for /myfavoritedrinks/aervoqirjvsergergs was...

It could, if you have caching strategy 'ALL' for `/myfavoritedrinks/`. @silverbucket what is the ticket where you have data not showing up in your app? Did you try out what...

could this be [the cache/fetch undefined bug](https://github.com/remotestorage/remotestorage.js/pull/781#issuecomment-57837637)?

I don't know, I just noticed the code looks wrong

> what does "simply deleting the foo/bar.txt task" mean? it's now [line 287](https://github.com/remotestorage/remotestorage.js/blob/master/src/sync.js#L287). updated the description. > Queuing a delete request? Deleting it from the remote? Deleting it at what...

indeed, we use asynchronous synchronization. see [`remoteStorage.sync.queueGetRequest`](https://github.com/remotestorage/remotestorage.js/blob/master/src/sync.js#L103)