When pushing or pulling translations, tags should be used to determine the scope of the operation. A mono-repo approach could lead to having several applications (i.e. backend, ui, admin-ui), which use different keys. Additionally, versioning can be done using this approach. Only relevant keys need to be pulled for a specific version. Tag management needs to be provided in the UI.
The config file translatr.yml should be enhanced to allow tagging.
When pushing, the related keys found in the targets should be tagged with the given tags (app:backend, version:1.0.0). When pulling, only keys with the given tags (app:backend, version:1.0.0) should be included.
When pushing or pulling translations, tags should be used to determine the scope of the operation. A mono-repo approach could lead to having several applications (i.e. backend, ui, admin-ui), which use different keys. Additionally, versioning can be done using this approach. Only relevant keys need to be pulled for a specific version. Tag management needs to be provided in the UI.
The config file translatr.yml should be enhanced to allow tagging.
When pushing, the related keys found in the targets should be tagged with the given tags (app:backend, version:1.0.0). When pulling, only keys with the given tags (app:backend, version:1.0.0) should be included.