feat(core,nestjs,docs): Finalize the async support effort started by #617 #622
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
Add promises to map method Add async handlers to mapAsync and mapArrayAsync
…e `mapDefer` usable for async approach
…lement full async capability
…ake NestJS `MapPipe` and `MapInterceptor` to call `mapAsync` instead `map`\n\n- Add possibility to fall back to synchronous mapping
…te documentation to cover the changes
…ert redundant changes\n\n- fix formatting
|
2 tasks
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.
Description
As a developer, I want to use input-output async operations while retrieving/resolving the values for the destination entity fields.
This initiative is a continuation/finalization of the initiative #617.
Proposed Changes
Checklist