I’m looking for a better solution for two things:
-
How can I understand if the data is fetched and ready, I use
BasicDealList.on("reset", function(){})to understand if the data is fetched from ajax and parsed and ready to be used but it feels dirty. -
If an empty JSON comes from fetching such as
{}, it still shows BasicDealList.length as 1 while it should be 0 thus I was forced to check if the first element is empty viacollection.length == 1 && jQuery.isEmptyObject(BasicDealList.toJSON()[0]which is very ugly.
Here is the code:
BasicDeal = Backbone.Model.extend();
BasicDealCollection = Backbone.Collection.extend({
model: BasicDeal,
url: '/some/ajax/url/',
});
BasicDealList = new BasicDealCollection();
BasicDealList.on("reset", function(collection, response){
isEmpty = collection.length == 1 && jQuery.isEmptyObject(BasicDealList.toJSON()[0]);
if (isEmpty){
// render no deal found html
}
else{
// render list of deals
}
}
BasicDealList.fetch();
If you don’t like listening for
reset, you can pass a callback directly to.fetch():If, later in your app, you want to know whether you’ve fetched the data already, you could usually just check
BasicDealList.length. If you want to avoid making repeated requests for collections that are actually empty on the server, you’ll probably need to work out a custom solution, e.g. setting a flag on.fetch():As for the empty data issue, you should be returning
[]from the server instead of{}. Backbone’s Collection callsthis.add(models, ...)within.reset(), and.add()checks whether themodelsargument is an array; if it’s not, it wraps it in one:So passing
{}will result inmodelsset to[{}], which is not what you want. If you can’t control the server, you could do the check for{}in a custom.parse()method, returning[]if it’s found.