ThePalaceProject / web-patron / 25053412715

88%

push

github

Snake_case in config docs, but also accept camelCase (PP-4124) (#128)

## Description

Consistency updates for configuration file handling:
- All user-facing configuration information (e.g., README, log messages, example configuration) specifies snake_case keys; and
- File/URL parsing accept both snake_case and camelCase values.
- All internal keys are camelCase, to align with JS/TS norms.

## Motivation and Context

Existing config files and documentation used an inconsistent mix of `snake_case` and `camelCase` keys (e.g. `gtmId` and `staticLibraries` were camelCase while most other keys were snake_case). This normalizes the user-facing convention to `snake_case` throughout while preserving backward compatibility with configs already using the camelCase forms.

[Jira PP-4124]

## How Has This Been Tested?

- New tests for key normalization helper and overall integration with `appConfig`.
- Manual testing in local development environment.
- All checks (tests, type checking, linter) pass locally.
- [CI checks](https://github.com/ThePalaceProject/web-patron/actions/runs/25012769122) pass.

## Checklist:

- [x] I have updated the documentation accordingly.
- [x] All new and existing tests passed.

196 of 220 branches covered (89.09%)

Branch coverage included in aggregate %.

23 of 23 new or added lines in 1 file covered. (100.0%)

307 of 344 relevant lines covered (89.24%)

31.27 hits per line