The application configuration file loader currently supports multiple file types with multiple file extensions, e.g. yml and yaml for YAML encoded data. This can 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 are no rules how to decide which extension takes precedence over another extension causing unexpected merged configurations.
To prevent such problems each file type will only support a single official file extension. The currently supported encodings are JSON and YAML where the following file extension will only be supported:
JSON
before: *.json
after: *.json
YAML
before: *.yml, *.yaml
after: *.yml
Note that this won't affect the precedences of different file types!YAML files will still take precedence over JSON files since YAML is a superset of JSON and JSON is also valid YAML.
The application configuration file loader currently supports multiple file types with multiple file extensions, e.g.
yml
andyaml
for YAML encoded data. This can 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 are no rules how to decide which extension takes precedence over another extension causing unexpected merged configurations.To prevent such problems each file type will only support a single official file extension. The currently supported encodings are JSON and YAML where the following file extension will only be supported:
*.json
*.json
*.yml, *.yaml
*.yml
Note that this won't affect the precedences of different file types! YAML files will still take precedence over JSON files since YAML is a superset of JSON and JSON is also valid YAML.