Better reusability of Content Block fields using GraphQL

[LarsDol]

Hi! Creating a little discussing regarding the new Content Block field in combination with the GraphQL API.

As far as I understand it's not really possible to create fragments for these fields, which is a bummer because it kinda hurts the benefits the field gives on the front-end side of things (besides that it's awesome in the CP itself).

I may just not know the way, so please enlighten me if I missed something. Else, would it be possible to create a separate interface for Content Block fields, so we can do something like this:

fragment ContentCollectionField on ContentBlock {
    fieldX
    fieldY
    entryField1 {
        id
    }
    entriesField2 {
        id
    }
}

query {
  entries(
    section: ["pages"]
    id: ["1"]
  ) {
    title
    id
    ... on default_Entry {
      contentBlocks {
      	... on contentBlocks_contentOverview_BlockType {
          
           contentCollection {
               ... ContentCollectionField
           }
        }
      }
    }
  }
}

This would greatly improve the DRY-potential for these fields in our front-end codebases and clean-up a whole lot of potential mistakes when editing fields that are reused in multiple entry types / matrix (neo) fields.

Let me know what you think, if such a thing would even be possible; or if there's another elegant solution at hand.

Thanks!
Lars

[LarsDol]

Ha! After some more digging I found the existing solution, which is actually quite close:

fragment ContentCollectionField on ContentBlockInterface {
    ... on contentCollection_ContentBlock {
        fieldX
        fieldY
        entryField1 {
            id
        }
        entriesField2 {
            id
        }
    }
}

Works like a charm. Closing this discussion, thanks for the 🦆

✌️