Repository navigation
Remove @translatableV2 from Category (catalog-dataplane) - #175
Conversation
Category tree values now come already translated from catalog-dataplane, so Messages must not wrap them a second time. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
Summary
@translatableV2fromCategory.name,titleTag, andmetaTagDescription(same schema change as [CATS-4817] Remove @translatableV2 from Category fields #172, after yanking0.73.0).vtex.search-resolvernow loadscategoryTreefrom catalog-dataplane (GET /api/catalog-dataplane/product/{id}), which returns these strings already translated — Messages must not wrap them again.Companion resolver: vtex-apps/search-resolver#612. Publish both apps together. (search-resolver should be executed first)
Test plan
product { categoryTree { name titleTag metaTagDescription } }on a localized binding and confirm catalog-dataplane locale values (no Messages encoding, no second translation).Brandand other@translatableV2fields are unchanged.categoryTreechange.Made with Cursor