settings for your Rual cluster.
order_description, and you can add a whole paragraph to that in the frontend, a few sentences long. Capitals, spaces and interpunction are added in the translation, like the text you are reading right now.
The translate menu will open, this is a modal with standard four
text area input fields each for its own language.
Translations are often context specific. That's why we have chosen to enable translations in the frontend. Once you have translated a specific key, it is used everywhere. So you don't have to track down every appearance on, for example, the field name
translate: by key which can be used in
uicomponent pins and
value: translate key which can be used in values. If you click on the
translation: key field in these blocks you can select one of the keys you already defined or define a new one. The system will show a menu like the one on the right, showing a line for every language that you have used in your cluster. This way you can add translations at once in the blueprint.
dynamic translations. In the picture to the right you see a combination of blocks where the content of field (in this case from our errormessages) can be set for translation.
failed pin gives an array of errors, each consisting of an object with the description of the error and the field name where the error occurred. Both need to be translated. Go to your
foreach function and change the concatenated values to translatable values. The
custom: value blocks in between are not empty, these contain a space so the concatenated text has proper spacing. Please note that we remove the
in: text that we used before.
Because we use the
value: translates we are not able to directly translate the value in the frontend. This is because the value translate is being translated in the backend and will send the translated value to the frontend, where the
ui translate will give you a custom translate element.
When you want to translate a value: translate, you have to know the key you want to translate and add it to a
ui: translate. When you have added it you can translate it either in the modal that opens in the blueprint, or in the frontend using (alt/option) + click and translate it in the modal that open.
The frontend modal also has a revert button, this will revert the translation back to the value that is saved with the key.
value: translate. What we want to do now, to make it really nice, is to show the error message next to the field, and to make the text red to draw more attention to it.