admin管理员组

文章数量:1297103

I'm trying to debug some missingKey warnings in my codebase and it seems that we're doing what essentially amount to t(t('some.valid.key')). The code is more complex which many layers between the first t() returning a translated string and trying to use it as a key in the second t(). For now, I've isolated and fixed my current issue by removing the extra call to t().

This wasn't initially detected since the translated text happened to be equal to the key in english. I believe it is an error to try and translate twice, unless there's some weird indirection usecase I'm not aware of. Is there a setting to enable such a warning? If not, would it be a sensible feature request?

本文标签: