From 8bdecadba47df905917773f03a48435d4bdd596f Mon Sep 17 00:00:00 2001
From: Pedro Lopez <pedroslopez@me.com>
Date: Fri, 13 Mar 2020 00:09:43 -0400
Subject: [PATCH] fix: don't call event handler for new messages directly to
 puppeteer

This was creating performance issues, specially on startup when the initial set of messages were being loaded for a client with many chats.
---
 src/Client.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Client.js b/src/Client.js
index 77f05f2..48ed38d 100644
--- a/src/Client.js
+++ b/src/Client.js
@@ -277,7 +277,7 @@ class Client extends EventEmitter {
         });
 
         await page.evaluate(() => {
-            window.Store.Msg.on('add', window.onAddMessageEvent);
+            window.Store.Msg.on('add', (msg) => { if(msg.isNewMsg) window.onAddMessageEvent(msg);});
             window.Store.Msg.on('change', window.onChangeMessageEvent);
             window.Store.Msg.on('change:type', window.onChangeMessageTypeEvent);
             window.Store.Msg.on('change:ack', window.onMessageAckEvent);