Update Invalid rename message format expected to be proper json (Koen…

…kk#3397) * Update Invalid rename message format expected to be proper json The example in the 'Invalid rename message format expected' error message, was not proper JSON and missing the last string end * Updates Co-authored-by: Koen Kanters <[email protected]>
lukyjay · Apr 20, 2020 · e1f9a39 · e1f9a39
1 parent c0ed4aa
commit e1f9a39
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -0,0 +1,5 @@
+{
+    "files.associations": {
+        "*.yaml": "home-assistant"
+    }
+}
diff --git a/lib/extension/legacy/bridgeLegacy.js b/lib/extension/legacy/bridgeLegacy.js
@@ -192,7 +192,8 @@ class BridgeLegacy extends Extension {
     }
 
     rename(topic, message) {
-        const invalid = `Invalid rename message format expected {old: 'friendly_name', new: 'new_name} got ${message}`;
+        const invalid =
+            `Invalid rename message format expected {"old": "friendly_name", "new": "new_name"} got ${message}`;
 
         let json = null;
         try {