You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Tests for the changes have been added (for bug fixes / features)
Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:
What is the current behavior?
In a transient injectable, the current instance is bound to the context in which it is instanciated.
However, there is no way I am aware of to configure the behaviour of the injected injectable at the intanciation level
What is the new behavior?
This PR introduce a way to achieve this intention by adding a new provider in the InternalCoreModule.
The injection of the INQUIRER symbol token results in the inquirer to be injected into our transient injectable.
@Inject(INQUIRER)inquirer
An example with a concrete business use-case is available in the PR
Does this PR introduce a breaking change?
[ ] Yes
[x] No
Other information
The way we implemented the feature may not be ideal given the architecture of the injection mechanism, so @millehorde and myself are willing to take all measures you consider appropriated
Aetherall
changed the title
Transient inject inquirer
feat(@nestjs/core): Add Transient Inquirer Injection
Mar 14, 2019
@Aetherall I am trying to better understand as an end user how/when/why I would use this since there is no documentation yet. I read through the specs/code, but still cannot figure out what is going on. Are you able to give a simple example of a situation where this feature would be a good use case? Thank you!
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?
In a transient injectable, the current instance is bound to the context in which it is instanciated.
However, there is no way I am aware of to configure the behaviour of the injected injectable at the intanciation level
What is the new behavior?
This PR introduce a way to achieve this intention by adding a new provider in the InternalCoreModule.
The injection of the
INQUIRER
symbol token results in the inquirer to be injected into our transient injectable.An example with a concrete business use-case is available in the PR
Does this PR introduce a breaking change?
Other information
The way we implemented the feature may not be ideal given the architecture of the injection mechanism, so @millehorde and myself are willing to take all measures you consider appropriated