feat(): add support for custom parsers #1647
Open
Conversation
This file contains hidden or 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
1 task
Member
|
@V3RON could you please rebase your branch |
This commit introduces a new configuration property named parser in ConfigModule, enabling the injection of custom parser functions. If not specified, the default implementation, backed by dotenv, is utilized. closes nestjs#1444
V3RON
force-pushed
the
feat/custom-parsers
branch
from
bf246e1 to
e6aacd8
Compare
Author
Done 🫡 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 commit introduces a new configuration property named parser in ConfigModule, enabling the injection of custom parser functions. If not specified, the default implementation, backed by dotenv, is utilized.
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?
The dotenv parser cannot be replaced.
Issue Number: #1444
What is the new behavior?
The parser may be changed by a module consumer. If it's not, then the default implementation backed by dotenv is used.
Does this PR introduce a breaking change?
Other information