Provide environment variables in configuration settings if present in… #226
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.
… process.env
Change Summary:
[ What have you changed and why? ]
I have changed the extension to allow user configurations to include
${env:myVariable}
in tag content definitions which will be replaced with environment variables available to the extension at runtime usingprocess.env
. This will be useful for automatic inclusion of a PHP project's version number which can be more easily automated as an environment variable than it can as a VS Code setting. Without this change I have to manually input the project's current version number for@since
and@version
tags. This also allows me to define more tag content at the User-level such as@copyright
and@package
by setting it to${env:PACKAGE_NAME}
and ensuring the directory provides this environment variable before VS Code starts.Checks:
CHANGELOG.md
updated with relevant changes