fix: allow Link and Array type references as variables

[elylucas]

Purpose

This PR allows a dev to set up variables that can bind to lists (arrays) and entry references as such:

variables: {
  // bind to a string list
  listText: {
    displayName: 'List Text',
    type: 'Array',
  },
  // bind to an entry reference
  entryReference: {
    displayName: 'Entry Reference',
    type: 'Link',
  },
  // bind to a list of entries
  listReference: {
    displayName: 'List Entry Reference',
    type: 'Array',
  },
}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
experience-builder-test-app	✅ Ready (Inspect)	Visit Preview	Jul 8, 2024 10:20pm

[primeinteger]

Should this PR be marked as a feat instead? Great work on this one! 🚀

[primeinteger]

It looks like the type for arrayValue is being inferred as any here. It might be nice to add a type argument so TS can help catch type errors if this code is updated in the future.

Suggested change

	const arrayValue = get(entryOrAsset, path.split('/').slice(2, -1));
	const arrayValue = get<Array<string | UnresolvedLink<'Entry' | 'Asset'>>>(entryOrAsset, path.split('/').slice(2, -1));

[primeinteger]

Suggested change

	console.warn(`Expected a value to an array, but got: ${JSON.stringify(arrayValue)}`);
	console.warn(`Expected a value to be an array, but got: ${JSON.stringify(arrayValue)}`);