From e1f9a3910d68f79df365d79e84f24342c99617ae Mon Sep 17 00:00:00 2001 From: Philipp Kolmann Date: Mon, 20 Apr 2020 19:38:55 +0200 Subject: [PATCH] Update Invalid rename message format expected to be proper json (#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 --- .vscode/settings.json | 5 +++++ lib/extension/legacy/bridgeLegacy.js | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 .vscode/settings.json diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000000..a04b21868b --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,5 @@ +{ + "files.associations": { + "*.yaml": "home-assistant" + } +} \ No newline at end of file diff --git a/lib/extension/legacy/bridgeLegacy.js b/lib/extension/legacy/bridgeLegacy.js index e9a260455b..c9615a54f0 100644 --- 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 {