Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
NICo currently ignores most unrecognized keys in its TOML configuration, including top-level keys and unknown keys in sections such as [site_explorer].
A typo, removed setting, or unsupported configuration can therefore be silently ignored while the service starts with an unintended effective configuration. This could cost many days of debugging effort, which makes configuration errors difficult to detect and may lead to operational surprises.
Feature Description
Add strict validation for carbide-api configuration files so unknown fields cause startup/configuration parsing to fail with an actionable error identifying
the invalid key and its section. Apply this consistently to the root configuration and nested configuration structs, with explicit compatibility exceptions
only where legacy keys must remain accepted. Cover the behavior with tests for top-level, nested, site-override, and environment-derived configuration.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
NICo currently ignores most unrecognized keys in its TOML configuration, including top-level keys and unknown keys in sections such as
[site_explorer].A typo, removed setting, or unsupported configuration can therefore be silently ignored while the service starts with an unintended effective configuration. This could cost many days of debugging effort, which makes configuration errors difficult to detect and may lead to operational surprises.
Feature Description
Add strict validation for carbide-api configuration files so unknown fields cause startup/configuration parsing to fail with an actionable error identifying
the invalid key and its section. Apply this consistently to the root configuration and nested configuration structs, with explicit compatibility exceptions
only where legacy keys must remain accepted. Cover the behavior with tests for top-level, nested, site-override, and environment-derived configuration.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct