[Feature Request] i18n support for error message

[jesseXu]

Feature description:

It would be good the error message has the i18n feature or can integrate with some i18n libs, then the error message can come out with different language support.

Problem it solves or use case:

Proposed implementation or solution:

This seems not an important feature or even shouldn't be done in this repo, still would be good to have some extra custom fields leave in violations that we can use it as a i18n key or something.

Contribution:

Can help for golang implementation if have a clear goal.

Examples or references:

Additional context:

[rodaine]

Totally agree, @jesseXu! We're exploring ways to make that happen. The ID on the violation is intended to be used as an i18n key, but we'll need to provide ways of translating the templates contained within the format CEL expressions and potentially include the rules that applied to the message or field that caused the violation (see #17)

[TENX-S]

Any updates?

[zishiguo]

Any updates?

+1

[rodaine]

Hi! The work in #265 is the first step in exposing the information necessary to support i18n. Once that functionality lands in the libraries, you'll be able to customize the validation errors appropriately.