Fix format violations and directory name vs schema key key mismatches

This commit is contained in:
jrb0001 2018-02-14 21:50:02 +01:00
parent f51fe91dbb
commit f52df83fbe
No known key found for this signature in database
GPG key ID: F67487D78E3BEB1F
17 changed files with 26 additions and 26 deletions

View file

@ -14,36 +14,36 @@ remarks: # option descriptions
: object required to have at least one
optional
: object not required to have at least one
+
single
: only one of this type allowed
multiple
: more than one of this type allowed
+
primary
: use field as lookup key for lookup
* only one allowed per schema
* does not allow newlines
+
schema
: use field name as the name of the schema
* only one allowed per schema
* does not allow newlines
+
lookup
: schema match to use for related record
+
\> option specs
: defines the option specifications for the key.
* must come last in option list
+
[label] string value. A positional string argument required.
Text inside brackets represent a label for the string.
If follwed by '...' values are gathered as an array.
+
{enum1|enum2|} enumeration. One option in pipe('|') deliniation is allowed.
If there is a trailing pipe it means the enum is optional.
+
label=str keyword argument. Label for value with type 'str', 'int', or 'decimal'
+
'literal' Literal value. literal text value.