Closed genericmoniker closed 7 months ago
Thanks for bringing this up! The easiest fix would most likely be to convert tuples to strings manually here: https://github.com/graphql-python/graphene-sqlalchemy/blob/2ca659a7840635a6058f032b9c00488534a07820/graphene_sqlalchemy/types.py#L382-L385
I'll check with the team to make sure this has no other implications and get back to you!
sorry for the long wait, this was fixed in #399
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics referencing this issue.
In #43 a change was made to convert composite keys to a tuple.
graphql-core made a change such that a tuple is no longer accepted as a valid ID (whereas it would previously just call
str
on the tuple).The result is an error such as the following when an object of the type is requested with its
id
field: