Fix environment variable substitution in .env files #766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #159
Summary
Fixed environment variable substitution in .env files by ensuring system environment variables are available during parsing.
Problem
When using environment variable substitution in .env files (e.g.,
PATH="${PATH};custom-path"
), system environment variables were not available for substitution. Only the launch configuration'senv
variables were passed to the parser.Solution
Modified
helper.ts
to mergeprocess.env
withdebugLaunchEnvVars
before passing to the env file parser. This ensures all system environment variables are available for substitution while still allowing launch config variables to override system ones.Test plan