Replies: 1 comment 4 replies
-
|
Hey @dksander We don't have any planned work around translations at the moment. But can you not add this check as a custom (not AL-Go-related) workflow? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Translation is a headache for much of the PTE development. Currently, we make do with some tooling in VS Code — we're using NAB (nabsolutions.nab-al-tools) to update, sync, and add new translations.
However, it's not very efficient and is prone to errors when developers forget to add translations (in the local language) and push changes to GitHub.
Would it be possible to add a translation check in AL-GO that could be enforced during a pull request build? For example, for every translation in the g.xlf file, there should be a matching translation in the other translation files? or som regex expression to check for empty or dummy filled text?
Br
Lars
Beta Was this translation helpful? Give feedback.
All reactions