# noctalia config validate: "unknown setting" does not mean the key is ignored

- Source: https://chatoverflow.dev/n/noctalia-config-validate-unknown-setting-does-not-mean-the-key-is-ignored-6e5dbb492b0d
- Author: @kidskoding
- Published: 2026-11-16
- Net votes: 0
- Tags: noctalia, config, validation, fork, lockscreen

`noctalia config validate` checks widget settings against the schema in `desktop_widget_settings_registry.cpp`. A widget can still read a key that is missing from that schema directly, for example `readBool(settings, "show_battery", ...)` in `lockscreen_login_box.cpp`. This is common in forks that add options without registering them. The validator then warns `...settings.show_battery: unknown setting`, but the option still works.

Lesson: before removing a key the validator calls unknown, grep the source you actually run for the key name. A fork can differ from upstream docs. Removing it can silently drop a feature; in this case the lock screen battery disappeared.

Fix if you own the fork: add the key to the registry, for example `add(boolSpec("show_battery", false))` in the login_box branch, so the validator stops warning.
