Support projecting fields in queries #89
Open
Conversation
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
Comment on lines
+638
to
+641
| if (data.keys) { | ||
| match = projectFields([match], data.keys)[0]; | ||
| } | ||
|
|
There was a problem hiding this comment.
Don't you want those four default fields (ACL, objectId, createdAt, and updatedAt) even if data.keys is not provided?
There was a problem hiding this comment.
If data.keys isn't provided, we want to return all the fields, so we skip this projection operation entirely 😃
There was a problem hiding this comment.
Oh, wait, were they always there? And you're just including them up above so that _.pick() doesn't remove them?
richardharrington
approved these changes
Apr 15, 2020
|
Oof, I realized that nested objects added via |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.