-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested properties #27
Conversation
Hi ! Is there any chance this can be reviewed and if it fit, merged ? If not, what can I do to make it mergeable ? |
Hi ! Is there any reason not to merge this one ? |
This may make no visible change to the API, but it does come with a performance hit. If this is to be merged, it needs to either (1) be a completely different code path that's enabled via an option like |
Thanks for the feedback. I will adjust the PR. I fear that the completely different path introduce too much complexity and maintainability drop. I'm not sure about the second option meaning (compile the accessor), what do you mean by compile ? Make the getattr a native function ? I just noted the benchmark task. I will try to find a solution with less performance hit. |
OK, I just:
|
<tr> | ||
<td valign="top">"nesting"</td> | ||
<td valign="top">boolean</td> | ||
<td valign="top">If <code>true</code>, nested fields will be available for search and sort using dot-notation to reference them.<br>ex:<code>nested.property</code><br><em>Warning: can reduce performances</em></td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nitpick: "performances" should be "performance"
Nevermind, will just fix this up in master :)
Looks great. Thanks for the PR! |
This pull request add support for searching and sorting on nested properties using dot-notation when declaring fields (ie.
nested.property
).I tried updating the documentation but I'm not sure on where to put this.
This pull request fix #26.