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.
What's this PR do?
Search fields is confusing and half broken; the
AND
was being discarded, and theOR
was not contained in a way that applying anAND
to it would have worked anyway, which is maybe why it got removed.This switches
search_fields
to a simplelist
instead of a confusingdict
and tweaks howq_objects
is built.Backwards compatibility with the old
or
dict is maintained, theand
continues to be ignored, docs have been updated to describe that this attribute should be a list.Where should the reviewer start?
View tests / query params.
Why is this important, or what issue does this solve?
Search fields was confusing and not working in some scenarios.
What Worf gif best describes this PR or how it makes you feel?
Tasks
README
updates reflecting any new features/improvements to the framework