Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Single configuration file extensions
The application configuration file loader supported multiple file types with multiple file extensions, e.g. `yml` and `yaml` for YAML encoded data. This could lead to priority problems when merging multiple loaded configuration states when there are multiple YAML files with different supported file extension in the same directory. There were no rules how to decide which extension takes precedence over another extension causing unexpected merged configurations. To prevent such problems each file type now only supports a single official file extension. The currently supported encodings are JSON (1) and YAML (2) where the following file extension are only supported: 1. JSON - before: `*.json` - after: `*.json` 2. YAML - before: `*.yml, *.yaml` - after: `*.yml` Note that this won't affect the precedences of different file types! YAML files still take precedence over JSON files since YAML is a superset of JSON and JSON is also valid YAML. References: (1) https://www.json.org (2) https://yaml.org Epic GH-33 Resolves GH-67
- Loading branch information