Hi! If I use Translate pipe for component input definition, extractor don't add a string in locale json.
Here is output of parseTemplate function:
As you can see, the first expression parsed is "ACCOUNT.TOKEN.IDS_TOKEN_PASSWORD_INPUT_TITLE" string, but in the template "ACCOUNT.TOKEN.IDS_TOKEN_TTL_INPUT_TITLE" string is higher
It will work if I will use plain interpolation template:
but that isn't thing I want to use, and I'm pretty sure it use to work. Plain "{{" "}}" template works because angular parser, using behind the scene, use a default InterpolationConfig like { start: "{{", end: "}}"}
@biesbjerg is there way to use regular input value definition with translate pipe
or I've missed something important?
Thanks!
Hi! If I use Translate pipe for component input definition, extractor don't add a string in locale json.
![image](https://user-images.githubusercontent.com/25117312/123825618-bb947800-d907-11eb-8fde-ad999a0ea0b6.png)
Here is output of parseTemplate function:
As you can see, the first expression parsed is "ACCOUNT.TOKEN.IDS_TOKEN_PASSWORD_INPUT_TITLE" string, but in the template "ACCOUNT.TOKEN.IDS_TOKEN_TTL_INPUT_TITLE" string is higher
![image](https://user-images.githubusercontent.com/25117312/123829326-09f74600-d90b-11eb-985b-d642643c2c89.png)
It will work if I will use plain interpolation template:
but that isn't thing I want to use, and I'm pretty sure it use to work. Plain "{{" "}}" template works because angular parser, using behind the scene, use a default InterpolationConfig like { start: "{{", end: "}}"}
@biesbjerg is there way to use regular input value definition with translate pipe
or I've missed something important?
Thanks!