Prior to 3.0, I could get all of the property data back. <div class="snippet-clipb

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

How do you write a query to pull back data for all properties? (Breaking Change 2.0 -> 3.0) about nikcio.uheadless HOT 1 CLOSED

nikcio commented on July 28, 2024

How do you write a query to pull back data for all properties? (Breaking Change 2.0 -> 3.0)

from nikcio.uheadless.

Comments (1)

nikcio commented on July 28, 2024 1

Hi @markadrake

Unfortunately to my understanding the GraphQL spec doesn't allow for infinite recursion you can read more here: graphql/graphql-spec#91 (comment)

But there's atleast two ways to workaround this issue:

If you like the old way of requesting data better you can overrride it. See an example of how to do it here: d5d2610

If you'd like to preserve the current way of querying you will have to manually nest the amount of levels deep you want to go into a block list. Let's say you for example don't use more than 3 levels deep nested block lists then you could do something like this:

{
  contentAtRoot {
    nodes {
      properties {
        value {
          ...propertyValues
        }
      }
    }
  }
}

fragment propertyValues on PropertyValue {
  ...allValues
  ... on BasicBlockListModel {
    blocks {
      contentProperties {
        value {
          ...allValues
          ... on BasicBlockListModel {
            blocks {
              contentProperties {
                value {
                  ...allValues
                  ... on BasicBlockListModel {
                    blocks {
                      contentProperties {
                        value {
                          ...allValues
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

fragment allValues on PropertyValue {
  ...basicValue
  ...contentPicker
  ...label
}

fragment contentPicker on PropertyValue {
  ... on BasicContentPicker {
    contentList {
      id
    }
  }
}

fragment basicValue on PropertyValue {
  ... on BasicPropertyValue {
    value
  }
}

fragment label on PropertyValue {
  ... on BasicLabel {
    label: value
  }
}

By keeping within the GraphQL spec you still have all the features that GraphQL brings. For example here I've set a label value to be aliased as label.

I hope this answers your question.

from nikcio.uheadless.

Recommend Projects