add support for multiple test env files #3846
Open
+94
−7
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.
This PR implements support for loading multiple environment files during test execution
New Setting: go.testEnvFiles
Added go.testEnvFiles setting that accepts an array of environment file paths
Allows loading multiple .env files in a specific order for test execution
Later files in the array override variables from earlier files
Backward Compatibility
Existing go.testEnvFile setting continues to work as before
Marked go.testEnvFile as deprecated with appropriate VS Code deprecation messaging
When both settings are used together, go.testEnvFile is processed after all files in go.testEnvFiles
Fixes #2473