Macro: t inside t causing ReferenceError: t is not defined about js-lingui HOT 3 CLOSED

Yup.string().matches(/^([0-9]{16})$/, t'${tFirst name}' must be ${16} characters.),

is it a real example? Still don't understand the need for using t in t.

This i suppose known issue, the macro treat {t`First name`} as a variable and keep it intact, so t is not transpiled.

May I ask what you expect to get in extracted messages in this case?

from js-lingui.

Hey, yeah, it is a real example... just migrating our legacy translation system to Lingui
old message format was UPPER_CASE and the second parameter was values e.g.

const FORM_MAX_CHARACTERS = "[FIELD] must be [NUM] characters";
t("FORM_MAX_CHARACTERS", { FIELD: t("FIRST_NAME"), NUM: 16 }

in the whole application, we are using Macro t and Trans and hash-generated IDs

I know I can use i18n._ but then I need to provide id which we don't want...

May I ask what you expect to get in extracted messages in this case?

basically {0} must be {1} characters

but if it is a limitation of babel-macro and there is nothing to do, then we can close it

from js-lingui.

Yeah, you probably can solve this differently in your code. This is not a limitation of babel-macro itself, rather how lingui macro is written, and i don't really want to touch it since it may break something else.

from js-lingui.