Issue with querying references in Sanity v3.47 resolved

Hello. I am having issues with querying references. I keep getting errors in parse response: I get response if query does not include references and weirdly the reference semi works when there is just one item not array of references. Anyone experiencing similar issues? I have just upgraded to v3.47.

Hey User! Can you send us over the query that is causing the issue?

*[_type == "platformHome"][0]{

_id,

title,

headline,

subheadline,

cards[]{

_key,

title,

subtitle,

platformLink->{"slug": slug.current}

}

}

I am trying to reference link to the page so I query said pages and extract just a slug. It was working before. I had the same issue with image url but it seems to be working now

If you remove all the fields like _id, title, etc and slowly add them back, which one causes the error?

I get response in studio. I use NextJS

At first glance that query looks right

I did it. Only platform link causes the problem

OH WAIT

I SEE

let me test something quick

When I do platformLink-> only, o don’t get the error. But once I query fields in that document it breaks

Just tested other fields. Only slug causes the problem.

platformLink->{slug}

does this work?

Ah okay heres why:

Haha. Just came upWith the same

so not working?

It’s working

Thanks! I used the other solution before and it was working so not sure what changed.

platformLink->{slug}
^^ This works because

slug

is a property of the object already,

slug: slug.current

isnt possible because its a circular dependancy. In Javascript you cant assign something to itself using its own value

No problem! If you did something like

url: slug.current

that would work

Assuming no other field is named url

I found

“slug”: slug.current

in documentation hence used it before. Good to know different approaches.

Really? That surprising that works (and tbh I might be completely wrong but in my brain it makes sense) lol

Can you share where thats from?

I’ll look it up. Can’t remember from top of my head.

Thank you!

But if you test it in studio you get correct response hence I never questioned it.

Hmmm thats wild, good chance my reasoning is wrong if it works inside of vision