Commit 008edbc
committed
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-671 parent 8531f47 commit 008edbc
2 files changed
+10
-23
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
56 | | - | |
| 56 | + | |
57 | 57 | | |
58 | 58 | | |
59 | | - | |
60 | | - | |
61 | | - | |
62 | | - | |
63 | | - | |
64 | | - | |
65 | | - | |
| 59 | + | |
66 | 60 | | |
67 | 61 | | |
68 | | - | |
| 62 | + | |
69 | 63 | | |
70 | 64 | | |
71 | | - | |
72 | | - | |
73 | | - | |
74 | | - | |
75 | | - | |
76 | | - | |
77 | | - | |
| 65 | + | |
78 | 66 | | |
79 | 67 | | |
80 | 68 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | | - | |
23 | | - | |
24 | | - | |
| 22 | + | |
| 23 | + | |
25 | 24 | | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
30 | 29 | | |
0 commit comments