Support escaping template variables in environment values #6935
+88
−5
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.
What's the problem this PR addresses?
Resolves #6491
How did you fix it?
Support escaping template variables in environment variable values. When a template variable is escaped with a backslash (e.g.,
\${VAR}
), it is now preserved as a literal string${VAR}
instead of being replaced with an actual environment variable value.I updated the regex to match values starting with a backslash. When a match starts with a backslash, it is treated as an escaped template and returns the value with only the backslash removed (
match.slice(1)
).Checklist