Now a unique conflict error will return ready to display messages.
To access it from in the front end you may need to use ValidationError.errors.email.message for users and ValidationError.errors.name.message for regions. This may be able to be bypassed somehow.
Now a unique conflict error will return ready to display messages. To access it from in the front end you may need to use ValidationError.errors.email.message for users and ValidationError.errors.name.message for regions. This may be able to be bypassed somehow.
This is what the object looks like:
{ "name": "BadRequest", "message": "regions validation failed: name: Region 'Heko' already exists.", "code": 400, "className": "bad-request", "errors": { "name": "message": "Region 'South Luke' already exists.", "name": "ValidatorError", "properties": { "message": "Region 'South Luke' already exists.", "type": "unique", "path": "name", "value": "South Luke" }, "kind": "unique", "path": "name", "value": "South Luke" } } }With the unique validator plugin you seem to only be able to edit the 'Properties' object Fixes #92