Gali Baum
Gali Baum
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
But notice that according to them best practice is to separate to fully self-contained strings
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
except maybe some formats, that might need some adjusting
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
We are using i18next, so what most of what they allow will work in novu
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
From what I can tell multiple contexts are not really supported by i18next. But, you can dig a bit deeper if they have a work around. Maybe this example could be a good lead (involving a var + context )
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
How is that @Dima_hat ? 🙂
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
{
"status": "status",
"status_busy": "busy",
"status_progress": "progress",
"welcome": "hello {{name}}, your status is: $t(login.status)"
}
{
"status": "status",
"status_busy": "busy",
"status_progress": "progress",
"welcome": "hello {{name}}, your status is: $t(login.status)"
}
in editor:
{{i18n "login.welcome" name="Gali" context=payloadStatus}}
{{i18n "login.welcome" name="Gali" context=payloadStatus}}
and in pauload you would add
{
payloadStatus: 'busy'
}
{
payloadStatus: 'busy'
}
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
is that what you were looking for?
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
and then in the editor you would use it like this:
{{i18n "conversations.inboxChange" firstName=actor.firstName statusVar="busy" }}
{{i18n "conversations.inboxChange" firstName=actor.firstName statusVar="busy" }}
16 replies
NNovu
Created by Dima_hat on 8/5/2024 in #💬│support
Using nested translation variables
Hi @Dima_hat You could try something like this: In your conversations translation file:
{
"newStatus": "bla bla {{statusVar}}",
"inboxChange": "{{firstName}} has changed the status to $t(conversations.newStatus)."
}
{
"newStatus": "bla bla {{statusVar}}",
"inboxChange": "{{firstName}} has changed the status to $t(conversations.newStatus)."
}
16 replies
NNovu
Created by ninadk on 3/17/2024 in #💬│support
User avatar not uploaded
@ninadk can you please try without the stringify of the body?
30 replies
NNovu
Created by ninadk on 3/17/2024 in #💬│support
User avatar not uploaded
let me know how that goes 🙂 @ninadk
30 replies
NNovu
Created by ninadk on 3/17/2024 in #💬│support
User avatar not uploaded
try adding to the trigger you are executing
novu.trigger(....,
payload: {...},
actor: { subscriberId: '2'} )
novu.trigger(....,
payload: {...},
actor: { subscriberId: '2'} )
30 replies
NNovu
Created by ninadk on 3/17/2024 in #💬│support
User avatar not uploaded
That will add the avatar of the actor, not the current subscriber https://docs.novu.co/additional-resources/glossary#actor
30 replies
NNovu
Created by ninadk on 3/17/2024 in #💬│support
User avatar not uploaded
No description
30 replies
NNovu
Created by Shaun on 1/19/2024 in #💬│support
Localize Date Strings with {{dateformat}}
No description
22 replies
NNovu
Created by Shaun on 1/19/2024 in #💬│support
Localize Date Strings with {{dateformat}}
Hi @jvinga , it should work, what is the error you are getting?
22 replies
NNovu
Created by Abhineet on 3/13/2024 in #💬│support
Tenant Support for frontend : React
@radek related to our discussion a few days ago
17 replies
NNovu
Created by jvinga on 3/6/2024 in #💬│support
I18n and translation files
we were about to use somehow same keys in different translation files so maybe the right approach would be to have like a big i18n files with different objects for each email?
Could you give an example? I'm not sure I follow 😬
6 replies
NNovu
Created by jvinga on 3/6/2024 in #💬│support
I18n and translation files
One reason being, when you're in the template, on the UI, there is no (apparent) ways to define which one you're using.
@jvinga what do you mean by that? In the ui you would use translationGroupName.translationKey for example {{i18n sign-up.welcome}}
6 replies
NNovu
Created by hajkowski.j on 3/6/2024 in #💬│support
Handlebars in email template
There shouldn't be a problem with this @hajkowski.j, it seems right. 1. If you are removing the {{#if aircraft}}Aircraft: {{aircraft}}{{/if}} part, is the update working? 2. Do you have any more steps in the workflow? Maybe its from a different content? 3. Are you using any variables in the subject/preheader?
4 replies