[4.1] Implement variable name whitelist #398
Merged
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.
It is now possible to tell the loader to only allow a predefined set of variables to be loaded. Since whitelisting is a kinda edge case requirement, I'll not be adding special
create
methods, like I did for choosing between mutable and immutable. Directly newing upDotenv
will be required. This is to keep the interface nice and simple for the majority of users.A full example is below, assuming the directory where the
.env
file is stored in$directory
and the array of allowed environment variable names (case sensitive) is in$whitelist
:// cc @ilimic1