How to get an awaited validation schema before passing to an action ?

[jeltehomminga]

First of all thanks for this great library!

I am using translated error messages in my zod Schema. To make my schema shareable between client and server I pass the translation function to a getValidationSchema function. To get my translations on the server side I first have to await my getTranslations function. I tried making a wrapper to do this, but got stuck and I am confused how to use the action after I got my shema in my async function

If someone know how I could do this please let me know. This is how my server action looks like

type EmailFormData = {
  newEmail: string
  confirmEmail: string
}

export type FormState = ZodIssue[] | EmailFormData

export const onSubmitEmailAction = async (prevData: FormState, actionData: EmailFormData) => {
  const { t } = await getTranslations('nl', 'myProfile')
  const schema = getValidationSchema(t)

  // how to use the action from the safe-action library here ?
}

[ali-alharthi]

I am facing the same issue. We use the same approach to translate zod validation errors rather than z.setErrorMap(...) which is more consistence for us and allows more customizable error translation IMO.
@TheEdoRan Any suggestions/plans to solve/support this?

Edit:
I believe if the schema supports async functions this would be solved (maybe?)

export const signIn = guestActionClient.
  schema(
    async () => {
      const t= await getTranslations('validation')
      return signInSchema(t)
    })
  .action(
    ...
  )

[TheEdoRan]

Thank you @ali-alharthi! So the problem appears to be that i18n JSON files are dynamically imported in getRequestConfig() and so getTranslations() from next-intl/server is async and has to be awaited, right?

[ali-alharthi]

@TheEdoRan correct, it must be awaited.

[TheEdoRan]

Will look into it soon, probably after v7 release. Thanks!

[ali-alharthi]

Understandable, thanks again for your time👍🏼

[TheEdoRan]

Quick update: I'm working on this feature right now, expect it to be implemented very soon in the library.

[TheEdoRan]

Implemented this feature in v7.0.0-next.51, and added a i18n recipe on the website too, to explain how this works in detail.
This will hopefully solve this issue and enable support for i18n solutions, but if you still experience problems feel free to leave a comment down here and I'll reopen this discussion, thanks!