How can we best support unopinionated i18n? #1276
ssalbdivad
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, although error configs like
problem
are English-specific, the finalArkErrors
instance returned by an invalid parse result can be directly introspected and mapped to localized errors as needed, usingerror.hasCode("min")
or similar to discriminate the error and access associated context.We need further documentation for these APIs (tracked in #1273), but based on some initial discussion, this may be sufficient to enable clean integrations with i18n libraries.
I wanted to open this discussion seeking other feedback on i18n and what we can do to make it as straightforward as possible without an opinionated solution.
Beta Was this translation helpful? Give feedback.
All reactions