Skip to content

fix: validate runtime settings before atomic replacement - #636

Merged
Sev7eNup merged 1 commit into
mainfrom
fix/611-valid-runtime-settings
Oct 24, 2026
Merged

Sev7eNup merged 1 commit into
mainfrom
fix/611-valid-runtime-settings

Conversation

@Sev7eNup

Copy link
Copy Markdown
Owner

What & why

Match configuration keys case-insensitively and merge disjoint case-variant sections when reading runtime overrides.

Validate serialized candidates with the production JSON configuration parser before changing the original or backups. Add regression tests for mixed casing and duplicate flattened keys.

Fixes #611

Testing

Api.Tests: FullyQualifiedName~RuntimeOverrides|FullyQualifiedName~EncryptingJsonConfigurationProviderTests|FullyQualifiedName~AdminSettingsControllerSectionTests|FullyQualifiedName~AdminSettingsRemainingSectionsTests|FullyQualifiedName~Backup — 260 passed. Regressions verify case-insensitive saves, merged disjoint sections, and rejection without changing the original or backups.

git diff --check passed. Full CI runs on this PR.

Match configuration keys case-insensitively and merge disjoint case-variant sections when reading runtime overrides.

Validate serialized candidates with the production JSON configuration parser before changing the original or backups. Add regression tests for mixed casing and duplicate flattened keys.

Fixes #611
@Sev7eNup
Sev7eNup merged commit 9b433e2 into main Oct 24, 2026
27 of 29 checks passed
@Sev7eNup
Sev7eNup deleted the fix/611-valid-runtime-settings branch October 24, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Saving settings can make a valid runtime configuration unloadable

1 participant