I've recently run into an issue fetching nested data within a content relationship field.
It was due to not being able to fetch all the RichText field in a fetch link query, so I had to use a Graph Query instead.
The problem I am facing is that there is no way (at least I don't think there is), to fetch the rest of the slices with something like ...slices.
Here you can see I have fetched the required nested content in a slice, but now it will only return this one slice.
Welcome to the Prismic community, and thanks for your feedback.
For the moment, you need to specify each slice name to retrieve them and retrieve different fields related to another document; you need to specify the content relationship name too. I agree with your feedback and added it as a product feature idea, but It's not on our roadmap for the moment.
While working on our project we're having the same issue. Is this feature on the roadmap, if so, when can we expect it to be released?
It would be nice that the graphQuery is not needed at all and that the data of the fields with a content relationship is retrieved automatically.
We understand your concerns and want to be transparent with our communications. Please note that the current functionality won't be changed, as each slice must be called individually, and there is no option to call them all with a single node name. Although GraphQuery syntax is similar to GraphQL, it is a separate tool.
I agree, being able to write something like ...slices is a badly needed feature. And weirdly on one of my custom types it seems to work without doing anything, and on others if I specify a slice for which I want specific content, then all other slices are just bypassed...
I don't understand how this can not be a basic feature of graphQuery. Especially given there's a limit to the number of characters in a graphQuery, if there are enough slices in a custom type it's not just verbose to specify each slice name, it might be impossible !!!
