Skip to content

Fixes Error Messages For Nested Blueprints

Compare
Choose a tag to compare
@losandes losandes released this 13 May 14:31

Registered blueprint error messages were different than simply nesting an object in a blueprint: the property names weren't qualified. This fixes that so properties that are validated against a registered blueprint have qualified error messages (i.e. instead of "expected id {null} to be {string}", we see "expected user.id {null} to be {string}").