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
It appears that our recent feature, enable_custom_operations, is not functioning correctly when we set async_client = false. Although the BaseClient is the synchronous version, the generated client is improperly using async def for its functions (e.g., async def query & async def mutation) when it should be using normal def.
The text was updated successfully, but these errors were encountered:
Yes, I am aware of this issue. In the first iteration, I did not plan to make custom operations compatible with async_client = false. This is not a bug; it is a feature that still needs to be implemented.
Thank you for pointing it out though! If you would like to contribute to this issue, please prepare a pull request for me to review and merge. Thanks!
Hello,
It appears that our recent feature,
enable_custom_operations
, is not functioning correctly when we setasync_client = false
. Although the BaseClient is the synchronous version, the generated client is improperly using async def for its functions (e.g.,async def query
&async def mutation
) when it should be using normal def.The text was updated successfully, but these errors were encountered: