fixes adding a component that has already been torn down

Author: justinbmeyer

can-component.js

@@ -339,6 +339,7 @@ var Component = Construct.extend(
 		// ### setup
 		// When a new component instance is created, setup bindings, render the view, etc.
 		setup: function(el, componentTagData) {
+			this._initialArgs = [el,componentTagData];
 			var component = this;
 			var options = {
 				helpers: {},
@@ -550,6 +551,7 @@ var Component = Construct.extend(
 
 			// Keep a nodeList so we can kill any directly nested nodeLists within this component
 			var nodeList = nodeLists.register([], function() {
+				component._torndown = true;
 				domEvents.dispatch(el, "beforeremove", false);
 				if(teardownBindings) {
 					teardownBindings();
@@ -585,11 +587,15 @@ var Component = Construct.extend(
 				}
 
 			}
+			component._torndown = false;
 		}
 	});
 
 // This adds support for components being rendered as values in stache templates
 Component.prototype[viewInsertSymbol] = function(viewData) {
+	if(this._torndown) {
+		this.setup.apply(this,this._initialArgs);
+	}
 	viewData.nodeList.newDeepChildren.push(this.nodeList);
 	return this.element;
 };

test/component-in-stache-test.js

@@ -77,7 +77,7 @@ QUnit.test("wrapped in a conditional", function (assert) {
 	assert.equal(fragment.textContent, "", "fragment ends without content");
 });
 
-QUnit.test("Component can be removed from the page", 2, function(){
+QUnit.test("Component can be removed from the page", 3, function(){
 
 	var ToBeRemoved = Component.extend({
 		tag: "to-be-removed",
@@ -104,11 +104,16 @@ QUnit.test("Component can be removed from the page", 2, function(){
 
 	var template = stache("<div>{{# if(show) }} {{{toBeRemoved}}} {{/ if}}</div>");
 
-	template({
+	var frag = template({
 		show: show,
 		toBeRemoved: toBeRemoved
 	});
 
 	show.set(false);
 	QUnit.ok(true, "got here without an error");
+
+	show.set(true);
+
+	prop.set(4);
+	QUnit.equal(frag.firstChild.getElementsByTagName("to-be-removed")[0].innerHTML, "4");
 });