From 4305fe0bcd53ec5a22930f6598450a2dfebaf9c3 Mon Sep 17 00:00:00 2001 From: Jeremy Wall Date: Mon, 26 Nov 2018 21:42:12 -0600 Subject: [PATCH] DOCS: document the strict mode behavior for env variables. --- docsite/site/content/reference/expressions.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docsite/site/content/reference/expressions.md b/docsite/site/content/reference/expressions.md index 1056248..716d473 100644 --- a/docsite/site/content/reference/expressions.md +++ b/docsite/site/content/reference/expressions.md @@ -53,8 +53,10 @@ tuple."quoted field"; There is a special selector in ucg for obtaining a value from the environment. The `env` selector references the environment variables in environment at the time of the build. You reference an environment variable just like it was in a -tuple. Attempting to reference a variable that doesn't exist will be a compile -error. +tuple. By default, attempting to reference a variable that doesn't exist will +be a compile error. You can turn this behavior off with the `--nostrict` +argument to the compiler. When in nostrict mode nonexistent variables will +result in a warning and be set to the NULL empty value. ``` let env_name = env.DEPLOY_ENV;