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
Hello, we are exploring Strawberry as an option of our application. We have several DynamoDB single-tenant database deployments for an object say "users". The users table has 10 columns that are the same between each deployment but there are more than 20 other columns that can be different.
For example in Deployment 1 the users table has columns/fields:
friends
last_logged_on
Deployment 2 might have
siblings
cousins
Therefore we have to determine the schema for Strawberry at runtime. Is there any documentation on this? We've tried several options suggested through GPT and looked into "hacking" into the StrawberryDefinitions class. The problem is that the return type of a query field must be compatible with Strawberry
Hello, we are exploring Strawberry as an option of our application. We have several DynamoDB single-tenant database deployments for an object say "users". The users table has 10 columns that are the same between each deployment but there are more than 20 other columns that can be different.
For example in Deployment 1 the users table has columns/fields:
Deployment 2 might have
Therefore we have to determine the schema for Strawberry at runtime. Is there any documentation on this? We've tried several options suggested through GPT and looked into "hacking" into the StrawberryDefinitions class. The problem is that the return type of a query field must be compatible with Strawberry
The last
get_dynamic_types
is incompatible asAny
is not supported.Feature Request Type
Description
The text was updated successfully, but these errors were encountered: