Currently, the schema definitions use inline objects for the asset metadata and asset preview fields. This is incompatible with "strict schemas", which prevents a GraphQL API from being deployed.
This PR moves those types to separate, named object types (shopify.assetMetadata and shopify.assetPreview).
I'm not super familiar with how data flows in these shopify scenarios - is data imported or created in-studio? If imported, we should check what the source puts into the meta._type and preview._type fields - they should (preferably) be shopify.assetMetadata and shopify.assetPreview, or alternatively not be present.
Currently, the schema definitions use inline objects for the asset metadata and asset preview fields. This is incompatible with "strict schemas", which prevents a GraphQL API from being deployed.
This PR moves those types to separate, named object types (
shopify.assetMetadata
andshopify.assetPreview
).I'm not super familiar with how data flows in these shopify scenarios - is data imported or created in-studio? If imported, we should check what the source puts into the
meta._type
andpreview._type
fields - they should (preferably) beshopify.assetMetadata
andshopify.assetPreview
, or alternatively not be present.