Skip to content

Commit 27cb1c5

Browse files
committed
config: Remove "MAY support any valid values" sentence
This line landed in 718f9f3 (origin/pr/673) minor narrative cleanup regarding config compatibility, 2017-01-30, #673), but I'm not clear on the motivation. The wording reads to me like "you don't have to support valid values for platform-specific fields if you don't want to", but we already cover unsupported value handling with the "MUST generate an error when invalid or unsupported values are encountered" language separated out in c763e64 (config: Move valid-value rules to their own section, 2017-02-07, #681). This commit removes the ambiguous line. Signed-off-by: W. Trevor King <[email protected]>
1 parent 837ee76 commit 27cb1c5

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

config.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,6 @@ For Windows based systems the user structure has the following fields:
327327
## <a name="configPlatformSpecificConfiguration" />Platform-specific configuration
328328

329329
[**`platform.os`**](#platform) is used to specify platform-specific configuration.
330-
Runtime implementations MAY support any valid values for platform-specific fields as part of this configuration.
331330

332331
* **`linux`** (object, OPTIONAL) [Linux-specific configuration](config-linux.md).
333332
This MAY be set if **`platform.os`** is `linux` and MUST NOT be set otherwise.

0 commit comments

Comments
 (0)