8SELECT - Integration Documentation
8SELECTService Status
  • 8.HX PLATFORM
  • Shop Integration
    • 8.SDK Web (JavaScript SDK)
    • Widgets
      • βž•Add more elements, like custom headline
      • πŸ‘»Hide recommendation area in case there is no content
      • πŸ”ŽAdding widgets after 8.SDK was loaded
      • πŸ—ΊοΈInternationalization
    • Shopping Cart
    • Checkout Tracking
    • Product Export
    • A/B Testing
    • Single Page Application
    • Tag Manager
    • Data Privacy / Cookies / GDPR
  • Widgets
    • 8.SIMILAR
    • 8.SET
    • 8.SET Custom
    • Touchpoints
      • Product Page
      • Cart Layer
      • Cart
      • Content Page
  • Product Export
    • Data Transfer
    • File Format
    • Base Data
      • Details and examples
    • Fashion Content Pool
      • Details and examples
    • Image Bot
  • Sandbox
    • Demo-Integration
    • Demo-Mode
  • API
    • Changelog
      • 2.0.0
      • 1.0.1
    • General
      • Introduction
      • Authentication
      • Pagination
      • Exceptions
      • GraphQL Schema
    • Examples
      • 8.SIMILAR
      • 8.SET
      • 8.SET Custom
      • Product Page - All Content
  • API Tracking
    • Changelog
    • General
      • Introduction
      • Authentication
      • Context
      • User Identification
      • Event Validation
    • Events
      • view
        • How to evaluate if view event can be sent
        • User views 8.SET content
      • interact
        • User clicks on a product within 8.SET content
        • User adds a product to their card from within 8.SET content
        • Example what is not a product interaction
      • order
Powered by GitBook
On this page
  • Fixed Bugs
  • An empty result is now empty, before it contained an edge with null values

Was this helpful?

  1. API
  2. Changelog

1.0.1

Fixed Bugs

An empty result is now empty, before it contained an edge with null values

The productSets() query result would previously always include at least one β€” potentially empty β€” node. This caused unintended and confusing behaviour when an empty list would have been expected, e.g. there are no sets for the given product or the given product does not exist.

Example

query MyQuery {
  productSets(input: {queryType: SKU, value: "<non-existent-product-sku>"}) {
    edges {
      node {
        title
      }
    }
  }
}

8.API 1.0.0 had returned

{
  "data": {
    "productSets": {
      "edges": [
        {
          "title": null
        }
      ]
    }
  }
}

8.API 1.0.1 returns

{
  "data": {
    "productSets": {
      "edges": []
    }
  }
}
Previous2.0.0NextGeneral

Last updated 9 months ago

Was this helpful?