From 4b04c8b905b923826a73bd3fc3bc461db861072e Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 28 Mar 2019 23:50:01 +0100 Subject: [PATCH] :fire: Removes now obsolete i_like_to_be_pwned option --- README.md | 8 -------- vscode/config.json | 3 +-- 2 files changed, 1 insertion(+), 10 deletions(-) diff --git a/README.md b/README.md index a099b8e..205e2d7 100644 --- a/README.md +++ b/README.md @@ -132,14 +132,6 @@ authentication on the VSCode by setting it to `true`. **Note**: _We STRONGLY suggest, not to use this, even if this add-on is only exposed to your internal network. USE AT YOUR OWN RISK!_ -### Option: `i_like_to_be_pwned` - -Adding this option to the add-on configuration allows to you bypass the -HaveIBeenPwned password requirement by setting it to `true`. - -**Note**: _We STRONGLY suggest picking a stronger/safer password instead of -using this option! USE AT YOUR OWN RISK!_ - ## Embedding into Home Assistant It is possible to embed VSCode directly into Home Assistant, allowing diff --git a/vscode/config.json b/vscode/config.json index 7179eca..ebd32d7 100755 --- a/vscode/config.json +++ b/vscode/config.json @@ -40,7 +40,6 @@ "keyfile": "str", "packages": ["str"], "init_commands": ["str"], - "leave_front_door_open": "bool?", - "i_like_to_be_pwned": "bool?" + "leave_front_door_open": "bool?" } }