Are i18n messages designed for API responses? Is there no one for human customers who submit a form via browsers?

[tats-u]

i18n messages looks too mechanical to show as error messages of forms. Is there a plan to add those designed for such a purpose? e.g. "Please make sure your input has at least 8 characters."

[fabian-hiller]

You can fully customize the error message, even for i18n. Individual messages can be passed as an argument to most schemas
and actions, local error messages can be passed when calling any validation method like parse and global messages can be set with setGlobalMessage, setSchemaMessage and setSpecificMessage.

https://valibot.dev/guides/internationalization/

[tats-u]

Are the built-in messages intended for APIs?

[fabian-hiller]

What exactly do you mean by "API"? A web service like a REST API or the API of a client side TS library?

[tats-u]

I mean the former.

[fabian-hiller]

I think they work great for APIs, but our focus was more on providing a simple and language-neutral string representation of the expected and received input to provide all the necessary information to further process an issue, if necessary, to create custom messages on top of it.

[tats-u]

Thank you for your answer. I am glad to know the design intention of the messages.
As you know, I will pass my custom messages for application clients.