Skip to content

Commit

Permalink
Merge pull request #1212 from AkihiroSuda/features-annotations-avoid-…
Browse files Browse the repository at this point in the history
…confusion

features.md: add a note to avoid confusion about annotations
  • Loading branch information
utam0k committed Jun 23, 2023
2 parents 48415de + 2bd22fa commit da13364
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions features.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,8 @@ The `null` value MUST NOT be confused with an empty value such as `0`, `false`,
**`annotations`** (object, OPTIONAL) contains arbitrary metadata of the runtime.
This information MAY be structured or unstructured.
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).
However, annotations do not need to contain the possible values of the [`annotations` property of `config.json`](config.md#annotations).
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).

### Example
```json
Expand Down

0 comments on commit da13364

Please sign in to comment.