Invalid typing of useCurrentLocale() about next-international HOT 5 CLOSED

Oh I understand what you mean now, sorry. I'll make another fix for it.

from next-international.

Thanks, I've just released 0.9.2 which fixes the type bug. You could already pass a config parameter but the type was wrong.

from next-international.

Awesome! Thanks!

In the same spirit, getStaticParams does not take a config param to change the segment name which means that if you use a segment name that is different than "locale", it won't work.

from next-international.

getStaticParams doesn't need the segment name, as it uses directly the keys of the locales object from createI18nServer:

from next-international.

It does, the key returned by each object in the array is 'locale', which will match the path segment as per NextJs documentation.

In order for createGetStaticParams to work, it would need to be changed to something like this:

export function createGetStaticParams<Locales extends ImportedLocales>(locales: Locales) {
  return function getStaticParams(config?: I18nCurrentLocaleConfig) {
    return Object.keys(locales).map(locale => ({
      [config?.segmentName ?? DEFAULT_SEGMENT_NAME]: locale,
    }));
  };
}

from next-international.