Required field on relations

[cajoy]

I have model like

  "properties": {
    "id": {
      "type": "string",
      "id": true
    },
    "name": {
      "type": "string"
    },
    "currency": {
      "type": "string"
    }
  },
  "dataSource": "mongodb",
  "validations": [],
  "relations": {
    "user": {
      "type": "belongsTo",
      "model": "user",
      "foreignKey": "userId",
      "required": true
    }
  },

And user should be required for all records. But I can easilly create record without user. "required" is not working for related models.

May be I can create validator but I prefer native support.

Alex

[fabien]

There's currently no required option for relations, but it would certainly make sense to add one.

For now, the easiest validation you could implement would be on the foreignKey:

Product.validatesPresenceOf('userId');

[cajoy]

Thank you

[fabien]

In the future, I'd like to implement the following:

"relations": {
  "user": {
    "type": "belongsTo",
    "model": "user",
    "required": true
  },
  "files": {
    "type": "belongsTo",
    "model": "user",
    "minItems": 2,
    "maxItems": 10
  }
}

[BerkeleyTrue]

+1

[brainthinks]

I definitely agree that it would be more proper to have a "required" attribute on the relation object.

In the mean time though, you can add the foreign key as a property and set its "required" attribute to true. Using the example json you mentioned, it would look something like this:

"properties": {
    "id": {
      "type": "string",
      "id": true
    },
    "name": {
      "type": "string"
    },
    "currency": {
      "type": "string"
    },
    "userId": {
      "required": true
    }
  },
  "dataSource": "mongodb",
  "validations": [],
  "relations": {
    "user": {
      "type": "belongsTo",
      "model": "user",
      "foreignKey": "userId"
    }
  },

[cajoy]

Thanks. It is good solution for now. !

2014-10-20 13:59 GMT-04:00 mymainmanbrown notifications@github.com:

I definitely agree that it would be more proper to have a "required"
attribute on the relation object.

In the mean time though, you can add the foreign key as a property and set
its "required" attribute to true. Using the example json you mentioned, it
would look something like this:

"properties": {
"id": {
"type": "string",
"id": true
},
"name": {
"type": "string"
},
"currency": {
"type": "string"
},
"userId": {
"required": true
}
},
"dataSource": "mongodb",
"validations": [],
"relations": {
"user": {
"type": "belongsTo",
"model": "user",
"foreignKey": "userId"
}
},

—
Reply to this email directly or view it on GitHub
#505 (comment).

[YoungsoonLee]

It's good~! thank you ~!

[mattiaaccornero]

+1

[solenovex]

+1

[davetayls]

+1 thanks for the tips above

[immo-huneke-zuhlke]

Thanks for these important hints.

However, unless I have misunderstood something, this trick (creating a required property that matches the name of the custom foreign key in a relation) only works if:

a) you also specify the type of the property - "any" will do, particularly if the id of the related model is an object identifier. If the type is omitted, the API explorer does not work at all.

b) the name of the id property in the related model is "id". This is crucial - none of the relationship code in LoopBack seems to work if you decide that you want a field called, for example, "name" to be the primary key. The only exception to this that I have discovered is that you can explicitly name the primary key field of a model called "size", for example, "sizeName" and then specify that as the custom foreign key.

Even then, I find that the API Explorer ignores the "include" filter for relations of type "hasOne", while it works for "belongsTo".

If I have misinterpreted something here, please correct me!