Changes to "config" between 2018-07-03 20:49:35 and 2018-07-03 20:49:59

36
37
38
39
40
41
42
43

44
45
46
47
48

49
50
51
52
53
54
55
36
37
38
39
40
41
42

43

44
45
46

47
48
49
50
51
52
53
54







-
+
-



-
+







  * And `value:` just sets a default.


## Storage and key name:

Notably this scheme just defines a list of available options. It does **not**
prescribe if they're stored in an `.ini`, `.json`, `xml` or code file, or a database
perhaps.
perhaps.  

Applications might utilize different stores even, and dispatch depending on
the `name:` syntax

  * For instance `name: ALL_UPPERCASE` might become a code constant,
  * For example `name: ALL_UPPERCASE` might become a code constant,
  * While `name: sectioned.feature.option` indicated an INI setting,
  * Or `name: "$cfg.plugins[after][]"` even a literal code target.

So names can be somewhat free-form. I'd avoid including the `$` sigil
however, or spaces obviously. Mostly-alphunumeric and dotted keys are
certainly most versatile.