Fix: Update translated slug #860
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request type
According to Storyblok's documentation, the path property should be used to create a story with a translated slug. However, when I tried to implement this as described, the API did not recognize path as a valid property. By using slug instead of path, I was able to create the translated pages successfully. It seems that the documentation is either outdated or incorrect regarding this point.
Please check the type of change your PR introduces:-->
How to test this PR
Add VITE_OAUTH_TOKEN and VITE_SPACE_ID to local .env and run e2e test.
What is the new behavior?
The path property has been renamed with slug for translated_slugs_attributes and translated_slugs to ensure compatibility with the API.