Files
frontend/src/features/settings
jakob.scheid 9ff74157e8 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.
2026-07-25 13:45:43 +02:00
..
2026-07-20 17:30:24 +02:00