Add support for filtering/omitting nested fields based on django style path expressions #16
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
|
I need this same functionality. Is there a reason why this hasn't been merged? It's been almost 3 months... |
|
@Kirkalicious see #18. Feel free to comment there :) |
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.
This PR attempts to add support for filtering nested fields using standard django style path expressions via the
__separator. One of the projects I am working on uses DRF in conjunction with mongoengine and being able to filter the nested fields is important for us as we end up with nested structures quite often that we filter at the mongo layer and without this we end up with fields coming back as null instead of removing them.