test(@nestjs/config) add more tests for priority #1666
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
I have a curiosity to see how config module works.
I think nestjs documents don't provide enough explanations.
If both .env file and load configration are provided, load configuration override .env vars?
If multiple load configrations are provided, last configuration take precedence?
That's why I add a couple of tests.
These tests answer following questions.
both .env file and load configuration, what's the priority?
multiple load configurations, what's the priority?
Does this PR introduce a breaking change?
Other information