Translation and the need of a format version #584
Description
Scenario where the ABAP object with translation is available in a gCTS managed git repository, say in format version 1.
During development the format version is increased to 2 and some changes have been committed to the git repository. Then, the metadata file (<object_name>.<object_type>.json) has formatVersion = 2, however the translation file is (implicitly) still format version 1.
Now, as the translation file is heavily linked to the metadata file through JSONPaths, the translation file is no longer meaningful/valid.
We consider to introduce a format version to the translation file to keep them in sync with the metadata file. Or to detect whether they are not in sync, and allow for a 'upgrade' of the translation files.
Properties file have comments. Every line that starts with # or ! is treated as a comment. Hence, we could add
# formatVersion=1
to the translation file.