From 76c740e90636a0dda3966a26c958c471ce952800 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Tue, 23 May 2017 21:43:24 -0700 Subject: [PATCH] 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 c763e641 (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 --- config.md | 1 - 1 file changed, 1 deletion(-) diff --git a/config.md b/config.md index 78de158cf..636cb1532 100644 --- a/config.md +++ b/config.md @@ -340,7 +340,6 @@ For Windows based systems the user structure has the following fields: ## Platform-specific configuration [**`platform.os`**](#platform) is used to specify platform-specific configuration. - Runtime implementations MAY support any valid values for platform-specific fields as part of this configuration. * **`linux`** (object, OPTIONAL) [Linux-specific configuration](config-linux.md). This MAY be set if **`platform.os`** is `linux` and MUST NOT be set otherwise.