Describe the Bug
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.
Describe the Bug
While working on #218 , I identified a bug where a query using
relay.ListConnectionunexpectedly generates twoDepartmentConnectionobjects 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.pyunder the nametest_query_with_secondary_table_with_values_list.