You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably more a question than a bug report, but you don't have a matching template for that, so I'll just go ahead here - sorry.
I have a content called news. Within this I have a field referencing a category. When inspecting it with graphql explorer I can see the ID of the referenced category by requesting the field field_category_string:
the relation gets resolved as expected but the field_category_string disappears as an option from graphql. This is very unfortunate since I need the category to query for news withing this category.
Or to re-phrase the question: How can I resolve relations and allow the entities to be filtered by such a resolved relation?
Describe the issue you're facing
This is probably more a question than a bug report, but you don't have a matching template for that, so I'll just go ahead here - sorry.
I have a content called
news
. Within this I have a field referencing a category. When inspecting it with graphql explorer I can see the ID of the referenced category by requesting the fieldfield_category_string
:Now, if I ask
gatsby-source-storyblok
to resolve this relation:the relation gets resolved as expected but the
field_category_string
disappears as an option from graphql. This is very unfortunate since I need the category to query for news withing this category.Or to re-phrase the question: How can I resolve relations and allow the entities to be filtered by such a resolved relation?
Reproduction
sorry...
Steps to reproduce
No response
System Info
Used Package Manager
yarn
Error logs (Optional)
No response
Validations
The text was updated successfully, but these errors were encountered: