Populate Nested refernces

[pehaada]

I was digging in the code and it appears that the ?populate feature will only work on top level documents. For example I have a Collection that contains 2 levels of nesting I'm not sure if I'm missing the way to populate nested values.

My Schema looks like the following

var CaseSchema = new Schema({
Plaintiff: {type: String },
Recipients: [RecipientSchema]
});

var RecipientSchema = new Schema({
service:{ type: ObjectId, ref: 'service' } ,
assignedId: {type: ObjectId},
Documents: [DocumentSchema],
});

I assume that out of the box I can't have MERS populate my service reference. I get the ID back but I have no way to specify the population of "nested" documents within Mongoose.

Thanks !
Adam

[jspears]

I started working on fixing that last week might have something next week
or two. I'll push a branch you can test against as soon as I have
something ready.

-js

Sent from my iPhone

On May 27, 2014, at 2:24 PM, pehaada notifications@github.com wrote:

I was digging in the code and it appears that the ?populate feature will
only work on top level documents. For example I have a Collection that
contains 2 levels of nesting I'm not sure if I'm missing the way to
populate nested values.

My Schema looks like the following

var CaseSchema = new Schema({
Plaintiff: {type: String },
Recipients: [RecipientSchema]
});

var RecipientSchema = new Schema({

service:{ type: ObjectId, ref: 'service' } ,
assignedId: {type: ObjectId},
Documents: [DocumentSchema],

});

I assume that out of the box I can't have MERS populate my service
reference. I get the ID back but I have no way to specify the population of
"nested" documents within Mongoose.

Thanks !
Adam

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/30
.

[pehaada]

I think there is still an issue w/ router.put. I think the difference is that I'm using ObjectID to reference my element VS an Index.

In router.put(reGet, function (req, res, next) {
var ObjectId = options.mongoose.Types.ObjectId;
...

I think the tobj should be tobj.set(ObjectId(last), body);

I'm guessing this may cause an issue if a custom ObjectID is used.

I was trying to dig up if mongoose provides a method to valdate an ObjectID.

Something like:
if (ObjectId.isValid(last)) {
tobj.set(ObjectId(last), body);
}
else {
tobj.set(last, body);
}