Skip to Content

ProductBundleContent

A product bundle content item with image, name, and value.

Type Definition

type ProductBundleContent { image: Image name: String value: String }

Fields

FieldTypeDescriptionNullableRelationship
imageImageThe image for this bundle content option.YesYes (to Image)
nameStringThe name for this bundle content option.YesNo
valueStringThe value for this bundle content option.YesNo

Relationships

  • image: Links to an Image object that represents the visual representation of this bundle content option. This relationship allows you to retrieve image metadata such as URL, alt text, or dimensions when querying a product bundle content item.

Usage Examples

Basic Query

{ productBundleContent { name value } }

Field Selection

{ productBundleContent { name image { url altText } value } }

Nested Queries

{ productBundleContent { image { url altText width height } name value } }

Filtering and Sorting

The ProductBundleContent type itself does not support filtering or sorting directly as it is typically nested within other objects. Filtering and sorting should be applied at the parent query level where ProductBundleContent is returned.

Implements

This type does not implement any interfaces.

Connections

ProductBundleContent does not have connection fields or pagination as it represents a singular content item within a bundle.

  • Image: Represents image data associated with the bundle content. Use this to access image URLs, alt text, and dimensions.

Best Practices

  • Always check for the presence of optional fields (image, name, value) before using them to avoid null reference errors.
  • When querying image, select only the fields you need (e.g., url, altText) to optimize query performance.
  • Use nested queries to retrieve detailed image metadata when displaying bundle content visually.
  • Since fields are optional, implement fallback UI or default values in your application for missing data.

Notes

  • The API currently requires no authentication, but this may change in future versions.
  • ProductBundleContent fields are optional, so clients should handle null values gracefully.
  • There are no computed or derived fields in this type.
  • No field arguments are defined for ProductBundleContent.
  • Performance is optimized by selecting only necessary fields, especially for nested image data.
  • This type is typically used within larger queries that return product bundles or related entities.
Last updated on