Patrick Radius

Hi @baalexander thanks for your clear answer. Glancing over the code i also noticed some parts could be improved, and especially with ES6 gives some nice opportunities for clean code....

Yes this would be very helpful but on an opt-in per query basis. So, sometimes the index has all the data the request needs, but other times another data store...

I also have this issue, but only when using it with the requirejs optimizer. But also with Marionette.

I wish i could, but i'm not sure how to set it up. Like i said it only happens when combining/compiling with the requirejs optimiser in my case. So just...

Yes, right... in theory any function that returns a promise-like ('thenable') object (such as jQuery's deferred) should work.. doesn't matter if the wanted list/collection already existed or will exist in...

Hmm, i do see a little buggy in it... i first get a dropdown with [object Object], etc... so i think i'm missing an 'else' clause somewhere... hmm the bug...

I'm not sure if stickit should 'fix' that or let it up to the user... I think supporting promises is still usefull, i use it now in our project similar...

I'm not sure if i understand your question. Which API should i layout? The PR still allows for using promises AND Deferreds... Your example like: `collection: function() { return $.getJSON('endpointToAnArray.json');...

It already checks for getting a collection.. that's supported. the 'issue' is that `Backbone.Collection.fetch()` does NOT return a collection... So, the `then` function _could_ wrap it in a generic `Backbone.Collection`...

> Wrapping in a generic Collection is backwards for the reasons you mentioned, but I think maybe allowing the user to pass back the collection directly should work: This should...