-
-
Notifications
You must be signed in to change notification settings - Fork 588
Treat empty string as valid translations (at least conditionally) #231
New issue
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
Comments
You're right, empty string shouldn't be an error ! Sorry about that, I think it's a regression |
SamVerschueren
added a commit
to SamVerschueren/ng2-translate
that referenced
this issue
Oct 4, 2016
ocombe
added a commit
that referenced
this issue
Oct 4, 2016
would you be willing to accept a PR that adds the suggested conditional switch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ...
Current behavior
If translation yields empty string, the translation is considered missing.
Expected/desired behavior
Empty strings, should either be considered valid translations always, or with a conditional switch, like
Reproduction of the problem
See this plunker
What is the motivation / use case for changing the behavior?
Use case is pretty much described in #223 . When localizing links, this is essential.
** Comments **
One could add a space there:
but this is error-prone as such kinda redundant whitespace can be lost when localization team does its job.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: