docs(microservices): add note on using AsyncMicroserviceOptions #3198
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 update clarifies the use of
AsyncMicroserviceOptions
for configuring microservices dynamically using theConfigService
when the injection context is available post-instantiation. The addition addresses scenarios requiring flexible configuration setup.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:
What is the new behavior?
Does this PR introduce a breaking change?
Other information
It is a long-standing question on StackOverflow that has been flagged for a solution, but the respective solution or explanation is absent in the official NestJS documentation. https://stackoverflow.com/questions/66605392