From eee75a4c020ea5bd900e57bdeda5c2fb89dc7e51 Mon Sep 17 00:00:00 2001 From: Dave Lee Date: Fri, 2 Feb 2018 13:07:05 -0800 Subject: [PATCH] Use new documentation wording for `config` --- Docs/ProjectSpec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docs/ProjectSpec.md b/Docs/ProjectSpec.md index 5d95af08..5d1058c5 100644 --- a/Docs/ProjectSpec.md +++ b/Docs/ProjectSpec.md @@ -427,7 +427,7 @@ targets: ### Common Build Action options The different actions share some properties: -- [x] **config**: **String** - All build actions can be set to use a certain config. If this is not set the first configuration found of a certain type will be used, depending on the type: +- [ ] **config**: **String** - All build actions can be set to use a certain config. If a config, or the build action itself, is not defined the first configuration found of a certain type will be used, depending on the type: - `debug`: run, test, analyze - `release`: profile, archive - [ ] **commandLineArguments**: **[String:Bool]** - `run`, `test` and `profile` actions have a map of command line arguments to whether they are enabled