ProductTaxonomyValue

Describes a product taxonomy value.

Type Definition

type ProductTaxonomyValue {
  translatedName: String
}

Fields

Relationships

• FilterValue.taxonomyValue: The ProductTaxonomyValue object is used as the type for the taxonomyValue field in the FilterValue object.
• ProductOptionValue.taxonomyValue: It is also used as the type for the taxonomyValue field in the ProductOptionValue object.

These relationships indicate that ProductTaxonomyValue provides taxonomy details related to filter values and product option values.

Usage Examples

Basic Query

{
  productTaxonomyValue {
    translatedName
  }
}

Field Selection

{
  productTaxonomyValue {
    translatedName
  }
}

Nested Queries

Since ProductTaxonomyValue only contains a scalar field translatedName and no nested objects, nested queries are not applicable.

Filtering and Sorting

The ProductTaxonomyValue type itself does not support filtering or sorting directly. Filtering or sorting would be applied on the parent objects such as FilterValue or ProductOptionValue that reference this type.

Implements

This type does not implement any interfaces.

Connections

ProductTaxonomyValue does not define any connection fields.

Related Types

• FilterValue: Contains a taxonomyValue field of type ProductTaxonomyValue.
• ProductOptionValue: Contains a taxonomyValue field of type ProductTaxonomyValue.

Best Practices

• Use the translatedName field to display localized taxonomy values in your UI.
• Since translatedName is optional, always check for null or undefined values in your client code to avoid runtime errors.
• Leverage the relationships from FilterValue and ProductOptionValue to access taxonomy information relevant to filters and product options.

Notes

• The translatedName field is a computed field that returns the localized name of the taxonomy value based on the current locale or language settings.
• This API currently requires no authentication, but this may change in future versions. Plan your integration accordingly.
• Because this type contains only a single optional scalar field, querying it has minimal performance impact.
• When using this field in large queries, consider caching results on the client side to reduce redundant requests.