From 44b2b950fd20e59fca1e6dddf522d456d2fd622f Mon Sep 17 00:00:00 2001 From: Roj Date: Thu, 8 Dec 2022 02:13:45 +0300 Subject: feat(cli): support configuring the lock file in the config file (#16781) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This allows the user to completely opt out from the lock file or rename it without having to use `--no-lock` and/or `--lock` in all commands. ## Don’t Use Lock File ```json { "lock": false } ``` ## Use Lock File With a Different Name ```json { "lock": "deno2.lock" } ``` The CLI args `--no-lock` and `--lock` will always override what is in the config file. Co-authored-by: David Sherret --- cli/schemas/config-file.v1.json | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'cli/schemas') diff --git a/cli/schemas/config-file.v1.json b/cli/schemas/config-file.v1.json index 26cd3ab77..7f6dcb4e3 100644 --- a/cli/schemas/config-file.v1.json +++ b/cli/schemas/config-file.v1.json @@ -355,6 +355,11 @@ } } } + }, + "lock": { + "description": "Whether to use a lock file or the path to use for the lock file. Can be overridden by CLI arguments.", + "type": ["string", "boolean"], + "default": true } } } -- cgit v1.2.3