Alternate File Configuration #64
Comments
Hi, If you think is a quite good thing, this can be an improvement. Today if the same key is found, the value is not considered. I can change the code to merge values instead. |
Hi, After a look it should work. |
I came across this thread and looking for a similar way to load json files that allows sharing of translated files with frontend libraries such as ngx-translate. They store files in i18n/{locale}.json format eg. i18n/en-US.json Sample JSON file:
|
Hi, Yep, currently it's impossible to have this format. To add this feature, this is a huge work in the JSON file loading process. |
Hi @AlexTeixeira, We are working with this format: View1.json{
"text_1": {
"Values": {
"en": "Englisht Text 1",
"es": "Spanish Text 1"
}
},
"text_2": {
"Values": {
"en": "English Text 2",
"es": "Spanish Text 2"
}
}
} We need to work with this format or similar: View1.es.json{
"text_1": {
"Value": "Spanish Text 1"
},
"text_2": {
"Value": "Spanish Text 2"
},
} View1.en.json{
"text_1": {
"Value": "Englisht Text 1"
},
"text_2": {
"Value": "Englisht Text 2"
},
} or simpler without "Value" node: {
"text_1": "Spanish Text 1",
"text_2": "Spanish Text 2"
} It would be possible? Thanks for considering my request. |
Hi, I let this issue open. When I will have some free time to work in this feature, I will try to add this feature. |
Hi @AlexTeixeira, Is this feature available? I only want to separate localization file by languages, the schema can be same. Thanks |
Hi everyone, The version 3.0.0-preview1 will have the I18n file configuration. I will set the release in final after your feedbacks. |
Great news! Thanks |
Hi, |
would you add support for an alternate file layout configuration?
example 1
Resources/localization.en-US.json
Resources/localization.fr-FR.json
example 2
Resources/en-US/localization.json
Resources/fr-FR/localization.json
The text was updated successfully, but these errors were encountered: