Discussion of unexpected behavior in Sanity v2.13.1 vs v2.7.4, fixed in 2.14.0

I’ve found an unexpected change in behaviour in Sanity v2.13.1 vs v2.7.4 (it’s been a while since I’ve upgraded).
I have a preview for an object type used in portable text that has a array of strings field. In the old version I could “select” this array and get the whole array of strings to use in “prepare”. In the new version the value passed to prepare is always undefined.

My preview code looks like this:

preview: {

select: {

name: 'name',

editors: 'editors',

},

prepare(selection) {

const { name, editors } = selection;

const editorsText =

!editors || editors.length === 0

? '(no editors selected)'

: editors.map((e) => programmingLanguageTitleForValue(e)).join(', ');

return {

`title:

${name || 'Untitled'} code for ${editorsText}

,

};`

},

},

Found another case where it’s easier for me to include the whole type to illustrate ^

This one now errors in the studio because

platforms

is undefined in prepare.

I’ve fixed these with the

select: { platforms0: "platforms.0" }

etc. approach.

I’d still like to know whether this is an expected change in behaviour. I think I was quite lucky to catch it when testing the upgrade.

Thanks for reporting! We have a PR to fix this issue 👍

Thank you 🎉

how did you fix this? I’m having the same issue but nothing is working

In my case there were only 4 possible values in the list so I could get away with this:

Based on the code you need to use if you have arrays of references:
https://www.sanity.io/docs/previews-list-views#dbe115bb1388
Seems likely it’ll be fixed soon though.

any updates on when this PR will get merged? Going on a week of busted previews for clients 😬

I’m seeing a similar issue, but instead of an array of strings, I have a string with an array of options. When selecting this field, it comes through as undefined in prepare. If I remove the ‘options’ block for my string field, the value shows up. Also using 2.13.1

So, common thread is not the array of objects, but the array of options for the string field.

This is fixed for me in the conditional-fields build that was released today!(

2.13.2-conditional-fields.29

)

https://sanity-io-land.slack.com/archives/CB4MVT2AE/p1627985808004500

This is fixed for me in the conditional-fields build that was released today.(

2.13.2-conditional-fields.29

)

https://sanity-io-land.slack.com/archives/CB4MVT2AE/p1627985808004500

would really love to see this addressed in an official release, still haven’t seen any version upgrades available in the CLI

would really love to see this addressed in an official release, still haven’t seen any version upgrades available in the CLI

Hi! This should be fixed in 2.14.0 that was released last week. Let me know if you’re still having problems 🙂