Wasp•10mo ago

How can I modify getVerificationEmailContent to support language-based email content?

Hello everyone,
I'm using Wasp's built-in authentication and have configured email verification in my main.wasp file. The functions getVerificationEmailContent and getPasswordResetEmailContent currently only accept an object with a verificationLink. However, I would like to send emails in different languages based on a language field stored in one of my database tables.

I've reviewed the documentation but couldn’t find a way to pass an extra parameter (e.g., the user's language) to these functions or to dynamically choose the email content based on the language.

How can I extend or modify these functions so that they can output different email content depending on the language specified in my database? Any guidance or pointers would be greatly appreciated.

Thank you!

kapa.ai•3/11/25, 10:48 AM

Hi @OopsIDeployed. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•3/11/25, 10:48 AM

----------------------
Based on the knowledge sources provided, there isn't a direct way to modify the getVerificationEmailContentgetVerificationEmailContent function to support language-based email content out of the box. However, I can provide some insights and potential workarounds based on the available information.

Currently, Wasp allows you to customize the content of verification and password reset emails by defining getEmailContentFngetEmailContentFn in your main.waspmain.wasp file. The function receives an object with a verificationLinkverificationLink (for email verification) or passwordResetLinkpasswordResetLink (for password reset) as its parameter.

Here's what you can do to potentially achieve language-based email content:

Create a custom sign-up action:You can create a custom sign-up action where you have more control over the email sending process. This is described in the [Creating a Custom Sign-up Action](<https://wasp-lang.dev/docs/auth/email#creating-a-custom-sign-up-action>) section of the Wasp documentation.
In your custom sign-up action, you can:
- Fetch the user's language preference from your database.
- Use this information to generate language-specific email content.
- Use the sendEmailVerificationEmailsendEmailVerificationEmail function to send the customized email.

Here's a simplified example of how you might structure this (note that this is not complete code and would need to be adapted to your specific setup):

```javascript
import {
createEmailVerificationLink,
sendEmailVerificationEmail,
} from 'wasp/server/auth'

export const signup = async (args, context) => {
// ... other signup logic ...

const user = await createUser(/* ... */)

// Fetch user's language preference
const userLanguage = await getUserLanguagePreference(user.id)

// Create verification link
const verificationLink = await createEmailVerificationLink(args.email, '/email-verification')

kapa.ai•3/11/25, 10:48 AM

// Generate language-specific email content
const emailContent = getLanguageSpecificEmailContent(userLanguage, verificationLink)

// Send the email
await sendEmailVerificationEmail(
args.email,
emailContent
)

// ... rest of signup logic ...
}

function getLanguageSpecificEmailContent(language, verificationLink) {
// Implement your logic to return language-specific content
// This could involve loading different templates based on the language
// or using a translation library
}

``

It's worth noting that this approach requires more custom code and doesn't use the built-in

``

It's worth noting that this approach requires more custom code and doesn't use the built-in

getVerificationEmailContent` function. However, it gives you the flexibility to implement language-specific emails.

For future improvements, there's an open GitHub issue discussing the introduction of a templating system for writing emails in Wasp, which might provide more flexibility in the future: Introduce templating system for writing emails in Wasp.

Additionally, the Wasp team is considering implementing a TypeScript-based configuration in the future, which could potentially allow for more dynamic customization options: GitHub Issue #551.

Remember that this solution is a workaround based on the current capabilities of Wasp. As Wasp evolves, there might be more straightforward ways to achieve language-based email content in the future.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•3/11/25, 10:48 AM

Sorry @OopsIDeployed, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

Filip•3/11/25, 1:59 PM

Unfortunately, I don't think this is possible with Wasp's built-in email support. You'd have to set it up yourself.

Let's wait for@miho to confirm whether I'm right

miho•3/12/25, 9:18 AM

Yeah... it seems we don't support it.

Because we are not giving you the user object, you can't decide per user what to send
Because it's not an async function, you can't use
```
prisma
```
```
prisma
```
or smth like that inside before returning the email.

@sodic should we create an issue for this? It feels like a minor change that could unlock users e.g. make it async at least?

Filip•3/13/25, 11:02 PM

We could, yes.

@miho Do you mind creating it? I think you have more context. I'm still a little fuzzy on the details

miho•3/17/25, 2:03 PM

Created an issue for this: https://github.com/wasp-lang/wasp/issues/2555

GitHub

Enable users to do more complex things in auth email templates · Is...

From a user on Discord: I'm using Wasp's built-in authentication and have configured email verification in my main.wasp file. The functions getVerificationEmailContent and getPasswordResetE...

How can I modify getVerificationEmailContent to support language-based email content?

Similar Threads

Similar Threads

Similar Threads