Conversation
…ame translationText when switching languages or generating translations
...l/components/translation-suggestions-dialog/translation-suggestions-dialog.component.spec.ts
Show resolved
Hide resolved
|
Coverage Impact Unable to calculate total coverage change because base branch coverage was not found. Modified Files with Diff Coverage (4)
🤖 Increase coverage with AI coding...🚦 See full report on Qlty Cloud » 🛟 Help
|
hirokiterashima
left a comment
There was a problem hiding this comment.
I was able to set up my testing environment, and I can see that the request/response to AWS's translation API is happening. I am seeing what looks like problems on the client-side.
After adding a new language (i.e., translations.ja.json file doesn't exist yet), I clicked on "Translate with AI" for a step title, and saw that all the fields on the step get populated with the translated text.
After this change, translations.ja.json looks like this:
{"undefined":{"value":"日本語","modified":1772495595914}}
It should look something like this:
{"v4oc25ub7l2ahozhdkwum4saew0qq0":{"value":"日本語","modified":1772495631120}}
In this example, "v4oc25ub7l2ahozhdkwum4saew0qq0" is the translationId that is defined in project.json, and it is used to uniquely identify the field that contains the text to be translated. Here's a part of the project.json, where the id is defined for the "title" field.
...
"title.i18n": {
"id": "v4oc25ub7l2ahozhdkwum4saew0qq0",
"modified": 1772495631087
}
...
It looks like this id is not being set properly when the translated text is saved in the project.ja.json file.

Changes
Test
Bug