Custom metadata for translation keys
in progress
Jakub Pomykała
We could allow users to add custom properties to translation keys and translations, store them in SimpleLocalize, and return them in the output. This feature might simplify some workflows by providing additional context or metadata, making it easier to manage/filter/sort on the client side.
Jakub Pomykała
marked this post as
in progress
Custom metadata are now working for 3rd party integrations like Shopify , and Webflow, and they will be implemented soon for other file formats like ARB, XLIFF and so on.
Jakub Pomykała
Merged in a post:
I don't see how to specify placeholders properties for ARB files, in particular "type"
F
Fractale
``` json
{
"@@locale": "en",
"deletionSuccessMessage": "{fileSizeDeleted} deleted successfully",
"@deletionSuccessMessage": {
"placeholders": {
"fileSizeDeleted": {
"example": "1.2 GB",
"type": "String"
}
}
},
}
```
I don't see how to specify placeholder properties for ARB files, in particular,"type"
Jakub Pomykała
Merged in a post:
Keep translation metadata from imported files
Jakub Pomykała
Store metadata from imported files (e.g.: 'translatable' for Android) and add them back during exports.