From 5f0ae93a1180da7dd8dc3e0ed69c4385774f9fd7 Mon Sep 17 00:00:00 2001
From: Mo Bitar <me@bitar.io>
Date: Sat, 14 Jul 2018 10:23:31 -0500
Subject: [PATCH] Reload component instead of activating on status change

---
 app/assets/javascripts/app/directives/views/componentView.js | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/app/assets/javascripts/app/directives/views/componentView.js b/app/assets/javascripts/app/directives/views/componentView.js
index b201c60a2..c8abd15bf 100644
--- a/app/assets/javascripts/app/directives/views/componentView.js
+++ b/app/assets/javascripts/app/directives/views/componentView.js
@@ -18,6 +18,7 @@ class ComponentView {
     $scope.el = el;
 
     $scope.identifier = "component-view-" + Math.random();
+    $scope.componentValid = true;
 
     // console.log("Registering handler", $scope.identifier, $scope.component.name);
 
@@ -112,7 +113,8 @@ class ComponentView {
 
       if($scope.componentValid !== previouslyValid) {
         if($scope.componentValid) {
-          componentManager.activateComponent(component, true);
+          // We want to reload here, rather than `activateComponent`, because the component will already have attempted to been activated.
+          componentManager.reloadComponent(component, true);
         }
       }