Skip to content

Commit 2c8feeb

Browse files
committed
config: Bring "unique... within this map" back together
Pull the empty-key restriction out into its own sentence (instead of leaving it in the middle of the uniqueness restriction). Drop the "best practice" portion, because the following line is "Keys SHOULD be named using a reverse domain notation...", which covers that idea more explicitly. Signed-off-by: W. Trevor King <[email protected]>
1 parent abfa798 commit 2c8feeb

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

config.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -393,7 +393,8 @@ If a hook returns a non-zero exit code, then an error is logged and the remainin
393393
This information MAY be structured or unstructured.
394394
Annotations MUST be a key-value map where both the key and value MUST be strings.
395395
While the value MUST be present, it MAY be an empty string.
396-
Keys MUST be unique and MUST NOT be an empty string within this map, and best practice is to namespace the keys.
396+
Keys MUST be unique within this map.
397+
Keys MUST NOT be an empty string.
397398
Keys SHOULD be named using a reverse domain notation - e.g. `com.example.myKey`.
398399
Keys using the `org.opencontainers` namespace are reserved and MUST NOT be used by subsequent specifications.
399400
If there are no annotations then this property MAY either be absent or an empty map.

0 commit comments

Comments
 (0)