You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on #218 , I identified a bug where a query using relay.ListConnection unexpectedly generates two DepartmentConnection objects when handling relationships involving a secondary table.
Upon investigation, it appears this issue originates from the Relay implementation rather than the secondary table logic itself. As a result, I’ve chosen to track and address this as a separate issue instead of including a fix in the original PR.
System Information
Operating system:
Strawberry version (if applicable):
Additional Context
A test case demonstrating this issue has been added to make debugging easier. You can find it in tests/relay/test_connection.py under the name test_query_with_secondary_table_with_values_list.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
The text was updated successfully, but these errors were encountered:
Describe the Bug
While working on #218 , I identified a bug where a query using
relay.ListConnection
unexpectedly generates twoDepartmentConnection
objects when handling relationships involving a secondary table.Upon investigation, it appears this issue originates from the Relay implementation rather than the secondary table logic itself. As a result, I’ve chosen to track and address this as a separate issue instead of including a fix in the original PR.
System Information
Additional Context
A test case demonstrating this issue has been added to make debugging easier. You can find it in
tests/relay/test_connection.py
under the nametest_query_with_secondary_table_with_values_list
.Upvote & Fund
The text was updated successfully, but these errors were encountered: