Remove query from public list when it's destroyed

Signed-off-by: Don Naegely <[email protected]>

src/js/cilantro/ui/query/list.js

@@ -33,7 +33,8 @@ define([
             sync: 'onCollectionSync',
             error: 'onCollectionError',
             request: 'onCollectionRequest',
-            destroy: 'onCollectionDestroy'
+            destroy: '_refreshList',
+            remove: '_refreshList'
         },
 
         itemViewOptions: function(model, index) {
@@ -74,15 +75,6 @@ define([
             this.checkForEmptyCollection();
         },
 
-        // When a model is destroyed, it does not call sync on the collection
-        // but it does trigger a destroy event on the collection. That is the
-        // reason for this separate handler. When a query is deleted, we will
-        // get the request event and then destroy event, there will never be
-        // a sync event in the case a user deleting a query.
-        onCollectionDestroy: function() {
-            this._refreshList();
-        },
-
         onCollectionError: function() {
             this.$('.empty-message').hide();
             this.$('.error-message').show();

src/js/cilantro/ui/workflows/workspace.js

@@ -107,6 +107,9 @@ define([
                     this.data.publicQueries.fetch({reset: true});
                 });
 
+                this.listenTo(this.data.queries, 'destroy', function(model) {
+                    this.data.publicQueries.remove(model);
+                });
             }
 
             this.listenTo(c.data.concepts, 'reset', function() {