Fixes #20466: Correct handling of assigned
filter logic
#20538
+1
−1
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.
Fixes: #20466
Summary
IPAddressFilter.assigned
to use the nested relationprefix
supplied by Strawberry‑Django.Q
, so when used under another filter (e.g.,Device → primary_ip4
), Django attempted to resolveassigned_object_id
on the outer model and failed.prefix
, ensuring the condition targets the nestedIPAddress
.Change
Why
Nested GraphQL queries like the example below errored due to the missing prefix; with this change they work as intended.
Follow‑up
@strawberry_django.filter_field
methods that construct rawQ(...)
lookups without applyingprefix
.