Based on early feedback from the recent release of inline blocks for Structured Text fields, we're introducing a small but impactful update to how our Content Delivery API handles them.

Previously, inline blocks were included within the blocks GraphQL selector. With this update, they now have a dedicated inlineBlocks selector:

Before the update:

1
query Before {
2
  blogPost {
3
    content {
4
      value
5
      blocks {
6
        __typename
7
        ... on BlockModelRecord {
8
          title
9
        }
10
        ... on InlineBlockModelRecord {
11
          title
12
        }
13
      }
14
    }
15
  }
16
}

After the update:

1
query After {
2
  blogPost {
3
    content {
4
      value
5
      blocks {
6
        __typename
7
        ... on BlockModelRecord {
8
          title
9
        }
10
      }
11
      inlineBlocks {
12
        __typename
13
        ... on InlineBlockModelRecord {
14
          title
15
        }
16
      }
17
    }
18
  }
19
}

Why this change?

By separating inlineBlocks from blocks, developers gain more precise control over rich text content, making it easier to manage and render structured text accurately, especially when using TypeScript. This improvement enhances both flexibility and consistency when working with inline blocks in GraphQL queries.

We appreciate your feedback and will continue refining the experience to make content management even smoother! 🚀