Revalidate page with localization enabled

[schlesingermatthias]

In your localization template example you revalidate pages like that

export const revalidatePage: CollectionAfterChangeHook<Page> = ({
  doc,
  previousDoc,
  req: { payload },
}) => {
  if (doc._status === 'published') {
    const path = doc.slug === 'home' ? '/' : `/${doc.slug}`

    payload.logger.info(`Revalidating page at path: ${path}`)
    revalidatePath(`${path}`)
  }
  ...

however this does not work for localized pages as the path to revalidatePath must be an exact one for revalidation to work and the path is not just the doc.slug but <locale>/${doc.slug}.

As far as I understand using
revalidatePath([locale]/${doc.slug}, "page") does not work, bc the slug being localized as well, nextjs will not find the folder in the filesystem (ie. folder might be called imprint but slug points to the German word Impressum)

What I came up with is looping through all locales and revalidating every path

export const revalidatePage: CollectionAfterChangeHook<Page> = ({
  doc,
  previousDoc,
  req: { payload },
}) => {
  const locales = ['de', 'en']

  if (doc._status === 'published') {
    const path = doc.slug === 'home' ? '/' : `/${doc.slug}`

    for (const locale of locales) {
      payload.logger.info(`Revalidating page at path: ${path}`)
      revalidatePath(`/${locale}${path}`)
    }
  }

but I'm wondering if there's a cleaner option? thanks in advance

[khnn]

I wrote a helper function which gets me the localized path with the locale and default slug as parameters, solving the issue of having localized slugs (impressum/imprint)
Alternatively, you could use invalidateTag instead of invalidatePath. It think its also used in the website template.