Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

translated_slugs is empty in resolved_relations when using graphql #884

Open
1 of 6 tasks
guanacone opened this issue Jan 6, 2023 · 0 comments
Open
1 of 6 tasks
Labels

Comments

@guanacone
Copy link

guanacone commented Jan 6, 2023

The issue occurs while working with: (check one with "x")

  • app.storyblok.com (CMS - Interface)
  • api.storyblok.com (CMS - Content Delivery API)
  • mapi.storyblok.com (CMS - Management API)
  • a.storyblok.com (CMS - Image Service)
  • storyblok.com (Website)
  • Other:

Current behavior:
Resolved relations in graphql don't provide the translated slugs

Expected behavior:
Resolved relations in graphql provide the translated slugs

Steps to reproduce:
A story has translated_slugs

Screenshot from 2023-01-06 11-23-57

When using this story as a relation in another story, even if the relation is resolved, the translated_slugs are not available.

Screenshot from 2023-01-06 11-26-54

The translated slugs are available when using the standard API:

https://api.storyblok.com/v2/cdn/stories/layout-default?resolve_relations=categories-section.categories&token=[STORYBLOK_PREVIEW_TOKEN]

Screenshot from 2023-01-06 11-30-20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant