.select workaround based on field names for find and findOne #63
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
|
Really sorry for the delay here - it seems that I am missing github notifications for this project. Anyways, I am not sure I quite understand the changes here. Could you explain to me what you are trying to achieve? Also, we would need a few tests for this feature to be merged in :) |
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.
Upon our needs for our business, I've made a workaround on .select with a pre-hook.
This hook automatically adds __enc_key and __enc_key_d for relevant fieldsToEncrypt.
Note: only works on top-level fields at the moment.
Doguhan