Different returning logic when using <Trans/> or t() function added by withTranslation hoc

Is your feature request related to a problem? Please describe. I wrote a component, which includes some common fields with translation on front-end side and additional fields, which I got from backend - their labels have already translated. So, if I use <Trans/> on pretranslated fields - I set this label on key attribute. Of course this key isnt found inside translation json and tag returns empty string. But when I use t() function added by withTranslation hoc - this function returns entered key string if key didnt find.

Describe the solution you’d like I would prefer to use standalone <Trans/> component instead a hoc (Code is cleaner, performance is better), so just return an entered key string with Trans, as you do it with t()

[jamuhl]

Depends on what the called function does (1 function calling 1000 functions might be slower than calling 100 functions calling no other functions 😁)

If you like you might provide a PR fixing the issue -> setting transEmptyNodeValue: false should return the key as is. Else I will try to fix this later this week.

[adrai]

@WebKieth any update on this?