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
there is a different product graphql type, one for products that uses ProductSchema and one that is used by SubscriptionInterface that uses ProductModel (does not have relations). This should become the same Type.
changed the title [-]Change productType in graphql to be based of ProductTable instead of ProductSchema[/-][+]Change productType in graphql to one Type[/+]on Aug 17, 2023
We do need the ProductModel graphql type because it is necessary for the auto registration of products to resolve correctly.
I believe the best approach is to update ProductModel to also have fixed_inputs, product_blocks and workflows, so we can add the GraphqlType ProductType to the ProductModel with ProductModel._strawberry_type = ProductType and will be resolved the same as root Products resource.
Activity
[-]Change productType in graphql to be based of ProductTable instead of ProductSchema[/-][+]Change productType in graphql to one Type[/+]tjeerddie commentedon Aug 18, 2023
We do need the ProductModel graphql type because it is necessary for the auto registration of products to resolve correctly.
I believe the best approach is to update
ProductModel
to also havefixed_inputs
,product_blocks
andworkflows
, so we can add the GraphqlTypeProductType
to theProductModel
withProductModel._strawberry_type = ProductType
and will be resolved the same as rootProducts
resource.[-]Change productType in graphql to one Type[/-][+][Maintenance]: Change productType in graphql to one Type[/+]