Validation only occurs at root level when there are nested Models

[mightyhawkins]

I have two Models defined; Location and Address, defined as follows:

"address": {
    "properties": {
        "address1": {
            "type": "string",
            "required": true
        }
    },
    "public": true,
    "dataSource": "db",
    "plural": "addresses"
},  
"location": {
    "properties": {
        "title": {
            "type": "string"
        },
        "address":{
            "type": "address",
            "required": true
        }
    },
    "public": true,
    "dataSource": "db",
    "plural": "locations"
}

When I Create an object based on the address Model via the API Explorer, the required constraint on address1 behaves as expected and I must supply a value to create the object.

When I Create an object based on the location Model via the API Explorer, the required constraint on the address works as expected, but the required constraint on the address1 of the address Model does not. I am able to create an address without an address1, which is not what I would expect.

I am using a memory datasource, node v0.10.24 and loopback v1.8.6.

[fabien]

@mightyhawkins here's a workaround for now:

Location.validatesPresenceOf('address');
Location.validate('address', function(err) {
  var address = this.address;
  if (address && ! address.isValid()) {
    var first = Object.keys(address.errors)[0];
    var msg = 'is invalid: ' + first + ' ' + item.errors[first];
    this.errors.add('address', msg, 'invalid');
    return err(false); // flag as error, but skip default error msg
  }
});

[fabien]

If you'd declare 'address' as an embedsOne (see #235) you'd have this kind of validation automatically.

[dhmlau]

@mightyhawkins, do you still have this problem? Does PR #235 help?
Since this issue was last updated more than 2 years ago, I'd like to close it.
Feel free to reopen if you still encounter this problem. Thanks.