Feature requests

Using the API for translation values, we can only receive what is currently saved in the editor environment. When a translation value is changed and therefore the review status of that translation changes to "NOT_REVIEWED" then the API will return this translation with the changed value and the "NOT_REVIEWED" review status. When filtering the API call to retrieve only "REVIEWED" translations (using the reviewStatus query parameter) the API won't return that translation at all. We would like to have a way to tell the API to respond only with "REVIEWED" translations, meaning not the currently saved value, but the latest value which was marked as "REVIEWED". Example: keys.label = "Foo" -> marked as "REVIEWED" User A changes keys.label to "Bar" keys.label is marked as "NOT_REVIEWED" API response now: keys.label = "Bar", marked as "NOT_REVIEWED" API response we want: keys.label = "Foo", marked as "REVIEWED"

It would be neat if we could add a flag when exporting to pull translations not from the editor stage but "latest" or "production" as this would allow to export e.g. the translations in a production stage as .properties for Java etc.

It should give the options of having only one file and use nested object in the json for namespace currently we can't use namespaces because hosting create separate endpoint for each, we update in locale storage at the app start and don't want to have to download 1 file per namespace (would need a list on the app or do weird things for it and many download instead of one call) would it be possible in the hosting to add in the index, the namespace if they exist as nested keys? that's how i18n do namespace in one file so it should be compatible with it at least, don't know about other lib