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
The handling of the validator messages is not good. We have to bridge between Stripes and Validator (in HibernateValidateFacet), which causes parameter replacement issues.
Validator has its own message interpolation system, which doesn't work with indexed params but with named placeholders. Moreover it doesn't display the field name by default.
In <= 2.0.3 we try to translate the messages using a correspondency map for message templates. We locate the template in the Stripes resources (don't even care about the Validator messages) and try to pass the replacement params.
We have inconsistent behavior depending on the platform : the parameters are not passed in the same order to the message template. We actually pass map keys, an unordered set, so it's a real bug in our code.
We need to find a better system, by using the Validator messages instead of our owns.
The text was updated successfully, but these errors were encountered:
The handling of the validator messages is not good. We have to bridge between Stripes and Validator (in HibernateValidateFacet), which causes parameter replacement issues.
Validator has its own message interpolation system, which doesn't work with indexed params but with named placeholders. Moreover it doesn't display the field name by default.
In <= 2.0.3 we try to translate the messages using a correspondency map for message templates. We locate the template in the Stripes resources (don't even care about the Validator messages) and try to pass the replacement params.
We have inconsistent behavior depending on the platform : the parameters are not passed in the same order to the message template. We actually pass map keys, an unordered set, so it's a real bug in our code.
We need to find a better system, by using the Validator messages instead of our owns.
The text was updated successfully, but these errors were encountered: