From 434d75f36281acc97133e7316f7f04927bfffc22 Mon Sep 17 00:00:00 2001
From: Michel Weststrate <mweststrate@fb.com>
Date: Mon, 27 Jan 2020 04:02:24 -0800
Subject: [PATCH] Always process messages for navigation plugin

Summary: For the navigation plugin we want to opt-out from the "enabled" and "process messages later" optimizations, because it's events should be immediately processed to reflect the changes in the topbar for navigation purposes

Reviewed By: jknoxville

Differential Revision: D19554297

fbshipit-source-id: 4bd49b5d1327feea6dea52e86d9dbc9d54a5dbee
---
 src/utils/messageQueue.tsx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/utils/messageQueue.tsx b/src/utils/messageQueue.tsx
index 365b73c0f..0090d403b 100644
--- a/src/utils/messageQueue.tsx
+++ b/src/utils/messageQueue.tsx
@@ -174,6 +174,7 @@ export function processMessageLater(
   const isSelected =
     pluginKey === getSelectedPluginKey(store.getState().connections);
   switch (true) {
+    case plugin.id === 'Navigation': // Navigation events are always processed, to make sure the navbar stays up to date
     case isSelected && getPendingMessages(store, pluginKey).length === 0:
       processMessageImmediately(store, pluginKey, plugin, message);
       break;
@@ -189,6 +190,7 @@ export function processMessageLater(
         ),
       );
       break;
+    // In all other cases, messages will be dropped...
   }
 }