Follow dotenv-flow variable precedence #492
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Follow dotenv-flow variable precedence when multiple env files are present. The order of precedence is as follows (Low to high): 1. Default env file (.env) 2. Local env file (.env.local) 3. Mode env file (.env.my-env) 4. Mode local env file (.env.my-env.local) 5. Command line variables
|
@goatandsheep I'd love if you could take a look when you get a chance. Thanks! |
|
Sorry it will take a little bit longer. This looks ok but I want to do some local testing |
|
i need a little bit longer. sorry for the delays. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Link to issue
Resolves #491
Description of changes being made
Change the order of merging multiple variables to:
Add test cases for the variable precedence.