From 167ddbfb4e429e47eceeb866a4bc0dec026f200f Mon Sep 17 00:00:00 2001
From: Jakob Scheid <jakob.scheid@icloud.com>
Date: Sat, 25 Jul 2026 13:45:43 +0200
Subject: [PATCH] fix(settings): fix handling of non-existent paths

Previously, the settings view now does not check whether the settings
content is falsy. But, if the setting does not exist, the setting itself
is undefined. So, if the specified settings path did not exist, an
error was thrown.
Now, the setting is checked for being falsy, not the setting content.
---
 src/features/settings/views/SettingsView.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/features/settings/views/SettingsView.vue b/src/features/settings/views/SettingsView.vue
index 7046bdf..4f0633a 100644
--- a/src/features/settings/views/SettingsView.vue
+++ b/src/features/settings/views/SettingsView.vue
@@ -44,7 +44,7 @@ watchEffect(() => {
 const updateSettings = function updateSettings () {
     if (activeSection.value) {
         const setting = getSettingRecursively(activeSection.value, settings.value);
-        if (!setting.content) {
+        if (!setting) {
             router.push('/settings');
         } else {
             activeSectionContent.value = setting;