Next Previous

Changes to "config" between 2018-07-04 14:36:50 and 2018-07-04 18:46:05

1
2
3
4

5
6
7
8
9
10
11

12
13
14
15
16
17
18
19
20
21
22
23
24

1
2


3
4
5
6
7
8
9

10






11
12
13
14
15
16
17



-
-
+






-
+
-
-
-
-
-
-








## # config:  {…}

The `config:` field is a list of entries describing feature- and
application-level settings.
The `config:` field lists feature- or application-level settings. It's often multiline:

    # config:
    #    { name: linky, type: bool, description: autolink urls }
    #    { name: xy.title, type: str, value: "blog title" }
    #    { name: perm, type: select, select: 3=USER|2=EX|1=SUP|0=KERN }

[PMD](wiki/Plugin+Meta+Data) is about uniform feature lookup. And
[PMD](wiki/Plugin+Meta+Data) is about uniform feature lookup and configurability. To keep it brief but support enough variation, each entry is a <acronym title="JSON, but quotes optional">JSOL</acronym>-dictionary.
plugin handling goes hand in hand with configuration management.
However it requires a structured field to avoid bulky definitions, yet
support enough variation.

Usually `config:` contains multiple indented lines, each being a
<acronym title="JSON, but quotes optional">JSOL</acronym>-dictionary.

#### {

<table class="cnt-tbl">
<tr>
   <th><code>name:</code></th>
   <td>associates some variable/constant/expression to a setting.</td>
︙