Mongoose - embedded documents are saved as string - node.js

Question

In my node app I have designation model with following Schema.
var DesignationSchema = new Schema({
_id : ObjectId,
designation : String
});
And this is embedded in users Schema.
var UserSchema = new Schema({
fname:String,
lname :String,
email :String,
password :String,
designations : [DesignationSchema]
});
User can select one / many designations from select list. Below is my jade implementation for creating select list;
select(name="designations")
- for(var i = 0; i < designations.length; i++) {
option(value="#{designations[i]}", name="designations[#{i}]") #{designation.designation}
- }
But these values are stored as string array instead of DesignationSchema array:
{
designations : ["{designation:'Some Value' , _id : __DESIGNATION__ID}", "{designation:'Some Value' , _id : __DESIGNATION__ID}"]
}
UPDATE
I am pushing designations in following way in expressjs :
var newUser = new User(user.info);
if(user.designations && user.designations.length){
for(var i =0; i < user.designations.length; i ++) {
newUser.designations.push(user.designations[i]);
//I have tried JSON.parse(user.designations[i]) but it raises error that says : 'Unexpected token d'
//user.designations[i] object is something like : {designation:'Some Content', _id : __DESIGNATION__ID}
//IMPORTANT : the __DESIGNATION__ID is not inside single (') or double (") quotes. And I think this is the reason why JSON.parse is raising the error.
}
}

Answer 1

You can ommit the _id from DesignationSchema as Mongoose will add that for you itself. Make sure you JSON.stringify the data you POST/PUT/etc so that you are left with something you can parse.
You may also need to specify the content-type as application/json when you send the data back. This should allow you to avoid JSON.parse in your endpoint.