Closed ersefuril closed 8 years ago
Thanks, this was actually a bug in the passing of messages to nested schemas, fixed in this commit:
5f6943c089096d148a394de2cf0cb797bb602d55
It is now working as expected as far as I can tell, re-open if you experience more bugs with this.
This fix is in the registry as 0.13.2
.
Closing as fixed.
Thanks for your fix :)
Please correct me if I'm wrong, documentation is not clear for me on a specific point. I tried to apply your example to override all error messages by custom messages.
So, here is your example :
I tried to clone all default messages and override them. I also tried to define only a small subset of messages to override, still have default error message. Maybe I did a mistake when redefining messages, so you can find a running example here :
https://tonicdev.com/ersefuril/5704d91504d77e13006a864f