Fix mapping of arrays with transform function #1
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
rojasraul
requested changes
Mar 18, 2023
| ) | ||
| o = keys.length ? await update(dest[ix], data, keys, context) : data; | ||
| else o = keys.length ? await update(null, data, keys, context) : data; | ||
| else o = keys.length ? await update(null, data, keys, context) : applyTransform(data, dest, context); |
Owner
There was a problem hiding this comment.
@Spencerhutch maybe the await statement is needed here
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.
Within the original node-object mapper there is issue #77 where when applying a transformation to an array the previous value of the transformation will be passed to the input of the next iteration of the transform. This PR is a copy of an existing open PR to node-object-mapper that has been stagnant for a year.