You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! 👋 Thanks for package!
I very likes use Nuxt Ui / Pro in my projects !
I use valibot in forms and set globally translation. ( please see reproduction )
Expected behavior: after set globally translation language in valibot, issues message shows in set globally lang Actual behavior: issues message shows in default language "en"
._parse is an internal API and should not be used directly. If you parse your schema with parse or safeParse, it should work as expected: https://valibot.dev/guides/parse-data/
For this reason we don't get messages with current translation.
ncodealex
changed the title
Problem with error translation if use valibot in form
Problem with error message translations if use valibot in form
May 12, 2024
Short explanation: Valibot captures the configuration when calling parse and safeParse and then passes it to ._parse. Since ._parse is called directly, the global configuration is probably ignored. I am happy to help with any questions.
Environment
Version
v2.16.0
Reproduction
https://stackblitz.com/edit/nuxt-starter-cf4613?file=app.vue
Description
Hello! 👋 Thanks for package!
I very likes use Nuxt Ui / Pro in my projects !
I use valibot in forms and set globally translation. ( please see reproduction )
Expected behavior: after set globally translation language in valibot, issues message shows in set globally lang
Actual behavior: issues message shows in default language "en"
Under the hood we used
._parse
method#https://github.com/nuxt/ui/blob/main/src/runtime/components/forms/Form.vue
Please see string 263.
fabian-hiller says:
For this reason we don't get messages with current translation.
Issue in valibot repo: https://github.com/fabian-hiller/valibot/issues/576
Please help with this problem, or if need i can try solve this problem and send new pull request!
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: