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

@@ -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;