Differentiation between undefined and blank translations

[blackmjck]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Blank translation strings (e.g. LANGUAGE.KEY: '') in a translation file result in a Missing translation for 'LANGUAGE.KEY' 🤔🕵🏻‍♀ console warning and a returned LANGUAGE.KEY value.

Expected behavior

It would be nice if the missing handler differentiated between missing values (where the key and/or value is undefined) and blank values (where the value is provided as a blank string).

What is the motivation / use case for changing the behavior?

It's a bit of an edge case, but we've been using it for years with ngx-translate to test for missing translation strings in non-English files.

If nothing shows up on screen for a given non-English run, then we know we're just waiting for the i18n team to finish making translations for that language. If APP.KEY shows up onscreen, then the dev team missed adding the key/string to the language file in question.

It's non-critical, but would be a nice to have as part of the migration path.

[NetanelBasal]

#43

[NetanelBasal]

You can use it with the latest version:

{
  provide: TRANSLOCO_CONFIG,
   useValue: {
	 ....
     allowEmpty: true
   }
  }
}