Skip to content

Commit 2bd22fa

Browse files
committed
features.md: add a note to avoid confusion about annotations
The "annotations" property in features.md is not expected to enumerate the possible values of the "annotation" property in config.md. Signed-off-by: Akihiro Suda <[email protected]>
1 parent 48415de commit 2bd22fa

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

features.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,8 @@ The `null` value MUST NOT be confused with an empty value such as `0`, `false`,
129129
**`annotations`** (object, OPTIONAL) contains arbitrary metadata of the runtime.
130130
This information MAY be structured or unstructured.
131131
Annotations MUST be a key-value map that follows the same convention as the Key and Values of the [`annotations` property of `config.json`](config.md#annotations).
132+
However, annotations do not need to contain the possible values of the [`annotations` property of `config.json`](config.md#annotations).
133+
The current version of the spec do not provide a way to enumerate the possible values of the [`annotations` property of `config.json`](config.md#annotations).
132134

133135
### Example
134136
```json

0 commit comments

Comments
 (0)