Passing non existing environmental variable to executable weird behaviour

When setting defaultEnv property with os_env that doesn’t exist, the environment variable will still be created, with not resolved string value.

For example

"catch2TestExplorer.defaultEnv": {
	"VAR_DOESNT_EXIST": "${os_env:VAR_DOESNT_EXIST}"
}

The literal resulting value passed to the executable would be VAR_DOESNT_EXIST == "${os_env:VAR_DOESNT_EXIST}".

[matepek]

I can see it is more logical in your case… But … considering

• "PATH": "${os_env:PATH}:${os_env:EXTEND_PATH_WITH_THIS}"
• "EXTENDED_VAR": "${os_env:SIMPLE_VAR} is extended with something".

In these cases I cannot unset PATH. Just wanted to say it is not trivial…

[matepek]

Note: new var is added @{os_env_strict:...}.