blog

commit

f327b687fe7d58dc8c2b6833f1d3fdc9a6847bbc

parent

d5a38e8a790d85c9b24b1b52af24cf013419da50

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2025-05-16 20:50

typos

Diffstat

1 files changed, 2 insertions, 2 deletions

diff --git a/_content/posts/2025-04-27-toml/index.md b/_content/posts/2025-04-27-toml/index.md

@@ -37,7 +37,7 @@ could be interpreted as a boolean, but also as a string, or a list with a
   37    37 single element. Based on that difference, the author has multiple complaints
   38    38 about TOML:
   39    39 
   40    -1 -   Users must know the correct types for value
   -1    40 -   Users must know the correct types for values
   41    41 -   Users must use quotes around strings and square brackets around lists
   42    42 -   Date-related types are bad for some reason
   43    43 -   The application still has to interpret values for types that are not
@@ -73,7 +73,7 @@ Combining multiple configuration files is important in two situations:
   73    73     apparmor profiles
   74    74 
   75    75 The concept of drop-ins is well established. I am not convinced that it should
   76    -1 be require for every single configuration file, but a lot of projects would
   -1    76 be required for every single configuration file, but a lot of projects would
   77    77 benefit from it. So I was a bit surprised when I learned that TOML does not
   78    78 allow overwriting values. (I was also surprised that this limitation is not
   79    79 even mentioned in the INI article.) TOML is compatible with the second use case