Ability for custom i18n language module

[hyunbinseo]

I would like to customize the Current KR (soon to be KO) i18n completely.

However, there doesn't seem to be a way provide a custom language translation.

import * as v from 'valibot';

// Import every translation for a specific language
import '@valibot/i18n/kr'; // since I don't want this

v.setGlobalConfig({ lang: 'kr' }); // I am setting kr as the global

// and setting specific error messages in the Language type
v.setSpecificMessage(v.minLength, (issue) => `Invalid length: ...`, 'en');

Is there a way for me to achieve this? A workaround would be fine.

You can use an objects or arrays to define your translations and then use JS code to dynamically call setSpecificMessage but this might break tree shaking.

[fabian-hiller]

Our i18n package uses the normal Valibot API. This means you can create your own translations if you want. Here is an example for schemas and the email action

import { setSchemaMessage, setSpecificMessage, email } from "valibot";

setSchemaMessage(
  (issue) => `유효하지 않은 타입: ${issue.expected} 을(를) 예상했으나 ${issue.received} 을(를) 받았습니다`,
  "kr"
);

setSpecificMessage(
  email,
  (issue) => `유효하지 않은 이메일: ${issue.received} 을(를) 받았습니다`,
  "kr"
);

You can define these translations in its own file and then import it like you import the official Valibot translations.

Does this solve your problem? Or did I misunderstand you?

[hyunbinseo]

Is setSpecificMessage the best option for now?

I want to define a translation for an entire language set.

I basically want to write a custom file like this and use it instead of defining one-by-one.

[fabian-hiller]

You can use an objects or arrays to define your translations and then use JS code to dynamically call setSpecificMessage but this might break tree shaking. Another option would be to use a script that transforms the object syntax into the Valibot API syntax.

[hyunbinseo]

Can you elaborate on the latter? I've added the former in the issue body.

[fabian-hiller]

We use a script that converts the object syntax (i.e. the link you shared) into Valibot API syntax. You can create your own script to do the same thing. It shouldn't be very complicated. Here is our script. Yours will probably be a lot simpler.

[hyunbinseo]

Didn't know that the i18n package used the same setSpecificMessage API:

import { setSpecificMessage, finite } from "valibot";

setSpecificMessage(

  finite,

  (issue) => `유효하지 않은 유한 숫자: ${issue.received} 을(를) 받았습니다`,

  "kr"

);

It's amazing how the above code is tree-shakable.

Still, it would be nice if there was an official guide to do this for all APIs without worrying about tree-shaking.

[fabian-hiller]

Great idea! If you figure it out (I am happy to answer more questions) we could write a new guide together or collect all the context in this issue and ask AI to write it for us.