Annick Walkenhorst

@SebbeJohansson but with `useStoryblok` and `useAsyncStoryblok` i do not get the relations as i described. How to achieve to also receive the `resolve_relations` when using these composables? i need to...

The interesting thing is, when i inspect the network tab... the response of the request is correct and contains the resolve relations, links & co. But the value the composable...

you can see it here at the end of the composable. ONLY the story gets returned. No chance to access the relations! From my perspective this is a Bug!

The current version i am using is: "@storyblok/nuxt": "^6.0.10",

In my project this appartements list: https://www.bivignano.com/en/angebot/appartements and the "Other appartements" at the bottom of an appartements detail like https://www.bivignano.com/en/angebot/appartement/hexenhaeuschen are made by relations. So this is really "needed" content....

This is the request: https://api.storyblok.com/v2/cdn/stories/angebot/appartements?language=de&version=draft&token=246y8yrGbIXVFeVVWldUnQtt&resolve_relations=AppartementReference.appartements i already provide the `resolve_relations` option. But in the response the relations info is part of `rels` outside of the story. the story itself does...

So the request itself is not the problem. Also the api options are not the problem. That is working fine! My problem is that the `useAsyncStoryblok` composable even if it...

> Hi! Yea it seems that @awacode21 is missunderstanding that the js-client automatically replaces the guids inside of the story object to contain the data from the rels. Everything _should_...

I close the issue as it seems it got fixed in the past. The ids for the relations in the story meanwhile get replaced with the actual relations data. So...

@xiaosasori thanks for the workaround. Do you know if custom collections were already working in 0.6.10 with same syntax? cause i don't get it running with 0.6.10