Migrate from Studio SDK v1 to SDK v2

• Overview
• What changed
  • Handling of Array/Link variable bindings
  • Utility methods to handle resolving Array/Link variable bindings
  • Utility methods to load additional entities into memory
  • Universal utility methods
  • Fixed semantics of useFetchBySlug() return values
• Change details for handling Array/Link variable bindings
• Migration checklist

Overview

At the heart of every website built with Contentful Studio is the Studio SDK. Over the last two years we’ve been making constant improvements to the SDK by adding some incremental features and fixing bugs.

During that time, we have also accumulated a list of improvements and fixes to the SDK which cannot be introduced in an incremental fashion and we need to bump a major version of the SDK to signal some breaking changes. However, in 98% of cases the upgrade from v1 to v2 should be as simple as a dependency bump.

Code and logic adjustments will be necessary only in the case when your website was relying on some specific niche features (eg. like using Link or Array variable bindings), or relied on some undocumented utility functions or logic.

This guide outlines the list of changes to help you understand the level of changes and whether any code and logic adjustments are required.

What changed?

Handling of Array/Link variable bindings

The most significant breaking change in the SDK v2 concerns the mechanism of how Array or Link variable bindings are passed into your React component props.

Let’s look at how receiving props when using Link variable binding used to work in SDK v1. Usually, your React component would have the following structure:

1
// First create definition for a component
2
// which let's Studio know that we want `myBlogPost` 
3
// prop to be bound to a link to an entry
4
const MyBlogPostComponentDefinition = {
5
  id: 'my-blog-post-component', 
6
  variables: {
7
    myBlogPost: {
8
      type: 'Link', 
9
    },
10
  },
11
};
12
13
const MyBlogPostComponent = (props)=>{
14
15
  const { myBlogPost } = props; 
16
  
17
  // You have access to flat properties of your entry
18
  const title = myBlogPost.fields.title;
19
  const intro = myBlogPost.fields.intro;
20
21
  // You have access to assets on your entry (assets are nested by nature)
22
  const imageUrl = myBlogPost.fields.image.fields.file.url; 
23
  
24
  // In SDKv1 the referenced entry myBlogPost.fields.author was
25
  // automatically downloaded and available as myBlogPost.fields.author
26
  // Thus it was fully legal to access referenced entries primitive 
27
  // fields and assets
28
  const authorName = myBlogPost.fields.author.fields.fullName;
29
  const authorImageUrl = myBlogPost.fields.author.fields.authorImage.fields.file.url;
30
  
31
32
  return (
33
   <div>
34
     <header>{title}</header>
35
     <pre>&#123;intro&#125;</pre>
36
     <img src={imageUrl}/>
37
     <div>
38
       written by <em>{authorName}</em>
39
       photo: <img src={autohrImageUrl}/>
40
     </div>
41
   </div>
42
  
43
  );
44
45
}

Note that in this example the React component has immediate access to:

• all immediate (flat) fields of the myBlogPost entry
  • myBlogPost.fields.title Text
  • myBlogPost.fields.intro Text
• the Asset present on the entry
  • myBlogPost.fields.image Asset (to get actual url of the asset you’d need to go deeper myBlogPost.fields.image.fields.file.url)
• the referenced entry (aka nested entry) (and all of its primitive and asset fields)
  • myBlogPost.fields.author
  • myBlogPost.fields.author.fields.fullName
  • myBlogPost.fields.author.fields.authorImage.fields.file.url (nested asset url)

Whilst availability of the immediate fields of the actual myBlogPost entry are expected to be there, the actual values of the referenced entries (eg. myBlogPost.fields.author) are “downloaded” and inserted instead of automatically linked. This happens because, behind the scenes, SDK v1 stitches together the tree of data. The “stitching” mechanism, takes the “head” entry myBlogPost and recursively follows its references (asset references like myBlogPost.fields.image or entry references like myBlogPost.fields.author ) and stitches together a tree of data.

The mechanism for this automatic data stitching provided some convenience in SDK v1, but it also introduced some disadvantages:

• The stitching mechanism was not rigorously defined, could have had inconsistent tree depth, mutated some entries in the store.
• It didn’t provide enough control over the stitching mechanism. For example, if your React component only needs 1 level of the entry, this stitching may not be required at all. Meanwhile, if your React component needs 3 levels of nesting, the stitching mechanism may not provide enough.

Also, there was a side effect: during the stitching, when receiving an entry into a component, it would mutate it from its original “unstitched” state which could cause some unexpected results in other components that were reusing the same entry.

To solve all of these issues, in SDK v2 we have introduced a stricter and more consistent mechanism for your React component props to receive bindings to entries when using Link/Array variable bindings. The binding mechanism now relies on these clear principles:

• All entries you receive are “shallow” (their reference fields are just links)
• All entries you receive are immutable (processed with Object.freeze() to ensure consistency)
• The stitching mechanism of your data tree is now a transparent mechanism that you can control and explicitly have to add to your components.

To migrate your website from SDK v1 to SDK v2, the most significant change would be changing and adding mechanism for “stitching” your data tree. We’ll provide more details on migration below. Meanwhile let’s outline some less impactful changes of the SDK v2.

Utility methods to handle resolving Array link variable binding

As the mechanism for “stitching” data for Array/Link variable bindings is now moved out the SDK and into React components, we provided a few methods to control and implement this mechanism.

One of the foundational steps for stitching data would be taking the reference and resolving it into the actual entry. To accomplish this in your React component, the following pattern can be used:

1
const MyComponent = (props)=>{
2
 const myBlogPost = structuredClone(props.myBlogPost);
3
 const title = myBlogPost.fields.title;
4
 const linkToAuthor = myBlogPost.fields.author;
5
 
6
 const authorEntry = resolveLinkToEntryInSomeWay(myBlogPost.fields.author);
7
 
8
 // you can use authorEntry directly
9
 console.log(authorEntry.fields.fullName);
10
 
11
 // or you can reinsert it into it's place in the entry
12
 myBlogPost.fields.author = authorEntry;
13
 
14
 return (<>
15
   ...
16
   <h3>Author: {myBlogPost.fields.author.fields.fullName}</h3>
17
   ...
18
 </>);
19
 
20
21
}

Note that the approach shown above relies on the resolveLinkToEntryInSomeWay() method.

In SDK v2 we provide such a method, as part of the new utility object that we expose, called inMemoryEntities. This utility object represents the concept of the “in memory entity store”. That store is preloaded by the SDK and contains all of the entities and assets referenced in the experience. Your React components have access to this store via the inMemoryEntities namespace or useInMemoryEntities.

1
import { 
2
  useInMemoryEntities, 
3
} from '@contentful/experiences-sdk-react';
4
5
const MyComponent = ()=> {
6
7
  const inMemoryEntities = useInMemoryEntities();
8
  
9
  // We have a variety of utility methods available 
10
  // on the `inMemoryEntities` which provide access to the 
11
  // "in memory entities store". 
12
  inMemoryEntities.maybeResolveLink();
13
  inMemoryEntities.maybeResolveByEntryId();
14
  inMemoryEntities.maybeResolveByAssetId();
15
  inMemoryEntities.hasAsset();
16
  inMemoryEntities.hasEntry();
17
};

1
import { 
2
  useInMemoryEntities, 
3
} from '@contentful/experiences-sdk-react';
4
5
const MyComponent = (props) => {
6
  ...
7
  const myBlogPost = structuredClone(props.myBlogPost);
8
  const inMemoryEntities = useInMemoryEntities();
9
  myBlogPost.fields.author = inMemoryEntities.maybeResolveLink(
10
    myBlogPost.fields.author
11
  );
12
  ...
13
14
  return <>
15
    ...
16
    <h3>Author name: {myBlogPost.fields.author.fullName}</h3>  
17
    ...
18
  </>
19
20
};

Utility methods to load additional entities into memory

When you load a webpage powered by the Studio SDK v2, it will load all the entities bound in that webpage. And it will also recursively download up to 3 levels of referenced entries (4 levels of assets).

This recursive downloading ensures that when your React component receives a prop, myBlogPost, enough of its references are already downloaded into the SDK memory and can be accessed by the React component, using inMemoryEntities.maybeResolveLink().

1
myBlogPost-> author   -> authorImage
2
LEVEL 2      LEVEL 3     LEVEL 4 
3
                         SDK downloads
4
                         assets only
5
                         on level 4

However, sometimes there may use cases, where your React components rely on even deeper tree of references available from the entry passed in via Link or Array.

The diagram below shows that in case your component wants to have access to deeply nested field like:

myBlogPost.fields.author.fields.authorCity.fields.country.fields.countryCode

You will not get such a deep entity automatically loaded by the SDK, but you will need to download it yourself. There’s a detailed guide on how to Manually download entries and assets into the SDK memory and how to use inMemoryEntities.addEntities() method.

However, manually loading such a deep data would be considered an anti-pattern and we’d advise to use it as a last resort.

1
myBlogPost-> author   -> authorCity      -> country
2
LEVEL 2      LEVEL 3     LEVEL 4         LEVEL 5
3
                         not downloaded  not downloaded
4
                         by SDK          by SDK

Universal utility methods

Many methods are implemented as TypeScript typeguards which will help with typing.

• The method isLinkToEntry() is added as the missing counterpart of the already existing isLinkToAsset() .

1
import { 
2
  isLinkToAsset,
3
  isLinkToEntry,
4
} from '@contentful/experiences-sdk-react';
5
6
if ( isLinkToEntry(anything) ) {
7
   assert(anything.sys.linkType === 'Entry');
8
}
9
10
if ( isLinkToAsset(anything) ) {
11
   assert(anything.sys.linkType === 'Asset');
12
}

There is also a minor improvement for the logic of isLink(): detection was made stricter. Now, it also expects target.sys.linkType defined (not just the presence of the target.sys.type === 'Link' ).

Fixed semantics of useFetchBySlug() return values

When using Contentful Studio you can publish a website which is pure React or NextJS with Server-Side Rendering (SSR). To publish production sites, most of our customers chose NextJS which conveniently allows rendering the initial version of the Studio website using SSR.

For the Studio SDK to render the website, it must first load the webpage data, meaning loading the experience. The SDK (since v1) provided two mechanisms to do that:

• useFetchBySlug() hook for pure React CSR sites
• fetchBySlug() method for NextJS SSR sites

In this SDK v2 we fixed small inconsistency in the return value of the useFetchBySlug() which affected only pure React SSR sites.

Previously, in the SDK v1:

1
...
2
export default Page(){
3
4
  const {
5
    experience,
6
    error,
7
    isLoading,
8
    mode,
9
  } = useFetchBySlug({
10
    slug,
11
    localeCode,
12
    client,
13
    experienceTypeId: config.experienceTypeId,
14
    hyperlinkPattern: '/{entry.fields.slug}',
15
  });
16
17
  // In SDK v1 
18
 
19
  // using `error` worked as expcted 
20
  if (error) ...
21
  
22
  // using `isLoading` worked as expected
23
  if (isLoading) ...    
24
  
25
  // when using `experience` you would always get an object
26
  // with single property { hyperlinkPattern }. You'd get
27
  // this object regardless of whether experience was truly loaded
28
  // or not.
29
  if (experience) {
30
     // this would always execute, regardless of the loading state
31
     // and will be experience === { hyperLinkPattern: 'some pattern'}
32
  } 
33
  else {
34
     // this would never execute
35
  }
36
37
}

In the SDK v2 we fixed the semantics of the experience variable:

• it will start as undefined
• and it will ONLY become defined when an experience is truly loaded when the webpage runs in “standalone” (outside of Studio editor iframe)
• the variable will still stay undefined in case the webpage runs inside of Studio editor iframe
  • PRO TIP: This is why in your Page components in pure React sites, you can use it to detect standalone mode e.g. if (experience) { do something only in standalone mode}

Let’s look at an example of how semantics of experience were fixed in SDK v2

1
...
2
export default PageThatIsClientSideReactComponent(){
3
  ...
4
  // extract url parameters  
5
  ...
6
  const {
7
    experience,
8
    error,
9
    isLoading,
10
    mode,
11
  } = useFetchBySlug({
12
    slug,
13
    localeCode,
14
    client,
15
    experienceTypeId: config.experienceTypeId,
16
    hyperlinkPattern: '/{entry.fields.slug}',
17
  });
18
19
  // In SDK v2
20
  // using `error` works as expected 
21
  if (error) ...
22
  
23
  // using `isLoading` works as expectd
24
  if (isLoading) ...    
25
  
26
  // as of SDK v2, during initial render the value of 
27
  // `experience`=== undefined
28
  // It only will become defined when two conditions happen:
29
  //  - page is running in standalone mode (aka outside of Studio Editor iframe)
30
  //  - experience was succesfully loaded
31
  if (experience) {
32
     // You are in "standalone mode" (which is sometimes called 
33
     // "Preview+Delivery mode" and experience was loaded.
34
  } 
35
  else {
36
     // This means that either experience wasn't yet loaded
37
     // Or we're running inside of Studio Editor iframe 
38
     // and `experience` variable will not be populated at all.
39
     // (This is because when SDK runs inside of Studio Editor iframe
40
     // the SDK doesn't need to load data itself, all data will be
41
     // provided by the parent frame).
42
     
43
  }
44
   ...
45
   return <div id="mypage"> ... 
46
     <ExperienceRoot experience={experience} locale={localeCode}/>
47
   </div>
48
}

Changes details for handling Array/Link variable bindings

• All entries you receive are “shallow”

In the SDK v2, when you receive a React prop (configured with Link variable binding) named myBlogPost the prop will have one of the two values:

• undefined in case user who uses Studio didn’t bind any data (or bound to an empty link, to a link to deleted item or to a link to archived item).

• “shallow” shape of the MyBlogPost entry (with unresolved links), e.g.:

1
...
2
// component definintion
3
  variables: {
4
    myBlogPost: {
5
      type: 'Link'
6
    }
7
  },
8
... 
9
const MyBlogPostComponent = (props)=>{
10
  const { myBlogPost } = props;
11
  console.log(`myBlogPost: `, myBlogPost);
12
  //... 
13
}
14
15
// And we expect console log output in SDK v2
16
// having reference fields as links
17
myBlogPost: {
18
  sys: {... },
19
  fields: {
20
    title: 'My blog post',
21
    intro: 'This is blog post about...',
22
    image: {
23
       sys: {
24
         type: 'Link',
25
         linkType: 'Asset',
26
         id: 'assetId123'
27
       },
28
    },
29
    author: {
30
       sys: {
31
         type: 'Link',
32
         linkType: 'Entry',
33
         id: 'entryOfAuthorId222'
34
       },
35
    },
36
  },
37
}

Note that every reference field of the myBlogPost entry (including asset reference, as assets are internally represented as references), is just a link. It’s not a real entry.

This is the main difference vs SDK v1, where every reference field of the entry would have actual resolved entry, similar to this shape:

1
...
2
// component definintion
3
  variables: {
4
    myBlogPost: {
5
      type: 'Link'
6
    }
7
  },
8
... 
9
const MyBlogPostComponent = (props)=>{
10
  const { myBlogPost } = props;
11
  console.log(`myBlogPost: `, myBlogPost);
12
  
13
  //... 
14
}
15
16
// And we expect console log output in SDK v1
17
// having reference fields resolve to entries
18
myBlogPost: {
19
  sys: {... },
20
  fields: {
21
    title: 'My blog post',
22
    intro: 'This is blog post about...',
23
    image: {
24
       ...
25
       fields: {
26
         file: {
27
           ... 
28
	         url: 'https://some-image-url',
29
         }
30
       },
31
    },
32
    
33
    author: {
34
       ...
35
       fields: {
36
         fullName: 'John Doe',
37
         authorImage: {
38
            ...
39
            fields: { file: { url: 'https://some-image-url' }}
40
         },
41
       },
42
    },
43
  },
44
}

In some simple cases your React component may be satisfied with just “shallow” entry, but in most of the cases you will want to have entire data tree stitched. In the SDK v2 we provide explicit tools - utility functions - which can help with that. We’ll describe the dedicated section further below.

• All entries your React component receives are immutable

In the SDK v2 when your React component receives a prop e.g. myBlogPost that has binding to Link variable type, the object you receive will be immutable. The entry is processed recursively with Object.freeze.

Thus, if you’re planning to mutate this object, you have to clone it first.

Example of using the value of the prop as normal for read-only use-cases:

1
...
2
// Example of using as read only
3
const MyBlogPostComponent = (props)=>{
4
  const { myBlogPost } = props;
5
  // fine to use myBlogPost as read only variable
6
  ...
7
  return <>...</>;
8
}
9
...

Example for use cases where you plan to mutate the entry

1
...
2
// Example of using myBlogPost for read/write use cases
3
const MyBlogPostComponent = (props)=>{
4
  const myBlogPost  = structuredClone(props.myBlogPost);
5
  // after cloning you can mutate any field or subfield of the obejct
6
  myBlogPost.fields.title = "Some new title"
7
  myBlogPost.fields.image = { ..., fields: { file: { url: 'https://new-image-url'}}}; 
8
  ...
9
  return <>...</>;
10
}
11
...

• Mechanism to “stitching” your data tree must be explicitly added to your components

When migrating from Contentful Studio SDK v1 to SDK v2, you have to alter the code of your React component to manually resolve field references for all the entries.

For example, when you’re creating a custom React component that uses binding, that binding will fall into one of the two categories:

1. binding to scalar variables
   • for example. Text (prop passed to component is string)
2. binding to objects (entries with references)
   • Link (prop passed to component is a JS object representing entry)
   • Array (prop passed to component is a JS Array holding entries, each of them is a JS-object representing an entry)

In case your React components used Link or Array variable bindings, then you’d need to add logic which “stitches” the data tree aka “resolve references”.

You can resolve single level of references explicitly, or you can do it recursively.

The principles of the changes are shown in the snippet below:

1
import type { Asset, UnresolvedLink } from 'contentful';
2
import { useInMemoryEntities } from '@contentful/experiences-sdk-react';
3
4
type ItemWithResolvedReferences = {
5
  sys: {
6
    id: string;
7
  };
8
  fields: {
9
    title?: string;
10
    description?: string;
11
    image?: Asset; // resolved asset, as opposed to unresolved link
12
  };
13
};
14
15
type ItemWithUnresolvedReferences = {
16
  sys: {
17
    id: string;
18
  };
19
  fields: {
20
    title?: string;
21
    description?: string;
22
    image?: UnresolvedLink<'Asset'>; // unresolved link to an asset
23
  };
24
};
25
26
type ItemWithManuallyResolvedReferences = Omit
27
<ItemWithUnresolvedReferences, 'fields'> & {
28
  fields: Omit<ItemWithUnresolvedReferences['fields'], 'image'> & {
29
    image?: Asset; // manually resolved asset
30
  };
31
};
32
33
type PropsV1 = {
34
  item: ItemWithResolvedReferences;
35
};
36
37
type PropsV2 = {
38
  item: ItemWithUnresolvedReferences;
39
};
40
41
// In SDK v1 the component receives an item, which is an Entry with resolved 
42
// references. Thus the image field is already an asset, not link to an asset,
43
// and thus can be used immediately without resolution.
44
export const ComponentUsingSdkV1: React.FC<PropsV1> = ({ item }) => {
45
  return (
46
    <div>
47
      <img 
48
        src={item?.fields.image?.fields.file?.url as string} 
49
        alt={item?.fields.title} />
50
      <div>
51
        <h3>{item?.fields.title}</h3>
52
        <p>{item?.fields.description}</p>
53
        <button> Explore </button>
54
      </div>
55
    </div>
56
  );
57
};
58
59
// In SDK v2 the component receives an item, which is an Entry with unresolved
60
// references. Thus the image field is a link object, which needs to be resolved
61
// and for convenience of access replaced with the actual asset object.
62
export const ComponentUsingSdkV2: React.FC<PropsV2> = ({ 
63
  item: itemWithUnresolvedReferences 
64
}) => {
65
66
  // Must make copy! as `item` is marked as immutable by the SDK v2
67
  const item: ItemWithManuallyResolvedReferences = structuredClone(
68
    itemWithUnresolvedReferences
69
    ) as ItemWithManuallyResolvedReferences;
70
  const inMemoryEntities = useInMemoryEntities();
71
  item.fields.image = inMemoryEntities.maybeResolveLink(
72
    item.fields.image
73
    ) as Asset | undefined;
74
75
  return (
76
    <div>
77
      <img 
78
        src={item?.fields.image?.fields.file?.url as string} 
79
        alt={item?.fields.title} 
80
       />
81
      <div>
82
        <h3>{item?.fields.title}</h3>
83
        <p>{item?.fields.description}</p>
84
        <button> Explore </button>
85
      </div>
86
    </div>
87
  );
88
};

Migration checklist

Here’s a quick checklist for migration:

• if you’re using Array or Link variable bindings you have to add to the component logic to resolve references or stitch the data tree that starts from the entity passed via Link binding (or an array of entities passed via Array binding).
• if you’re using useFetchBySlug() (which is rarely used in NextJS apps over preferred fetchBySlug()) you have to check that you’re not relying on experience being true all the time. And that your handling of useFetchBySlug() return values corresponds to the logic described earlier in this guide.