From a8d85403464474e31fc9e2f98e182071aec3ca90 Mon Sep 17 00:00:00 2001
From: Sam Machin <sam@sammachin.com>
Date: Sun, 31 May 2020 13:44:31 +0100
Subject: [PATCH] fix for settings.set subsequent updates

By cloning the value the assert.deepEqual will now fail even for subsequent updates of the value without restarting Node-RED
---
 packages/node_modules/@node-red/runtime/lib/settings.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/node_modules/@node-red/runtime/lib/settings.js b/packages/node_modules/@node-red/runtime/lib/settings.js
index 35417a497..e22a90686 100644
--- a/packages/node_modules/@node-red/runtime/lib/settings.js
+++ b/packages/node_modules/@node-red/runtime/lib/settings.js
@@ -87,7 +87,7 @@ var persistentSettings = {
             throw new Error(log._("settings.not-available"));
         }
         var current = globalSettings[prop];
-        globalSettings[prop] = value;
+        globalSettings[prop] = clone(value);
         try {
             assert.deepEqual(current,value);
             return when.resolve();