We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I use JSON files for translations, like
{ "application": { "formatter": { "name": "My application formatter", "desc": "Some explanatory description for the formatter" }, "v1": { "label": "Label for the version v1", "desc": "Description for this version", "fields": { "FirstVariableToSet": { "label": "MyVariable", "desc": "" } } } } }
I think it is absolutely valid to have an empty translation for a key, like application.v1.fields.FirstVariableToSet.desc.
application.v1.fields.FirstVariableToSet.desc
Unfortunately the key (and its value) is completely scrapped during message file import.
Culprit:
go-i18n/i18n/message_template.go
Line 37 in b42d9bd
Would it be possible to support empty message values in the future? Or maybe with a configuration parameter, whether they should be ignored or not.
The text was updated successfully, but these errors were encountered:
What problem does this cause for you?
Sorry, something went wrong.
No branches or pull requests
I use JSON files for translations, like
I think it is absolutely valid to have an empty translation for a key, like
application.v1.fields.FirstVariableToSet.desc
.Unfortunately the key (and its value) is completely scrapped during message file import.
Culprit:
go-i18n/i18n/message_template.go
Line 37 in b42d9bd
Would it be possible to support empty message values in the future? Or maybe with a configuration parameter, whether they should be ignored or not.
The text was updated successfully, but these errors were encountered: