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.
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
.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too