Skip to content

Filter nested objects #149

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Filter nested objects #149

wants to merge 1 commit into from

Conversation

whybin
Copy link

@whybin whybin commented Nov 23, 2017

This change would allow use of comparison operators at multiple levels of a deeply nested object; see #90. Original query rules still apply at deeper levels.

By default, filtering nested objects is disabled to ensure backwards compatibility.

I've added regression tests for filtering using the old behavior, as well as tests for nested query objects. All passed.

Allow implicit deep equality check of non-array objects and use of
comparison operators for deeply nested items, while preserving the
original query rules (negation, logical OR). Add a setting for this
behavior that defaults to false. Also provide tests for filtering nested
objects and regression tests.
@mmikowski
Copy link
Collaborator

@typicaljoe @whybin Looking into this now. @whybin thank you!

@Hermholtz
Copy link

Hi guys! Can this feature be merged finally?

@whybin
Copy link
Author

whybin commented Sep 11, 2018

IIRC this PR breaks filtering/comparison operators with arrays and may require considerable refactoring to preserve all intended behavior. I'm not inclined to fix those issues at the moment. If anyone else is interested, they are free to take a stab at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants