Subdocument IDs handling not clear

[mauriceKA]

I would like to have stable IDs (uuids) also on sub documents of a collection. This is what I experience:

Again, I have a simple model:

server.resource('test', { 
    p1: [{
        p2 : String,
    }]
});

Then, I want to give the documents under p1 a uuid. When I POST this example JSON ...

{
    "p1": [
        {
            "p2": "foo"
        }
    ]
}

... I get back a JSON like this immediately in the result:

{
  "p1": [
    {
      "p2": "foo",
      "_id": "573f04dccaa53f2c00925336"
    }
  ],
  "id": "e6b20bd0-6c18-4095-b729-bc1156e5fb2f"
}

Why is the inner ID called "_id" and not "id"? And why is the inner ID not in in UUID format like the outer ID but some internal (probably Mongo?) format?

When I query for it later, at least the "_id" field is now correctly called "id", but this is confusing. Why not already in the return of the POST? And again, the id is not a UUID.

{
  "p1": [
    {
      "p2": "foo",
      "id": "573f04dccaa53f2c00925336"
    }
  ],
  "id": "e6b20bd0-6c18-4095-b729-bc1156e5fb2f"
}

Also when I pre-generate a UUID and try to submit it along in the POST like ...

{
    "p1": [
        {
            "p2": "foo",
            "id": "2df2aa9e-1d4a-418b-9ecd-cd7f5de4bbd6"
        }
    ]
}

the UUID is overwritten and I get back a different, regular ID in the repsonse:

{
  "p1": [
    {
      "p2": "foo",
      "_id": "573f06ebcaa53f2c00925337"
    }
  ],
  "id": "8587bb44-ebe6-4db7-9532-7e7fa02ba36e"
}

Could you fix this, so that also for sub-documents UUIDs are generated?

[zackyang000]

_id should be remove, I will add a field named id which generated by UUID to instead of it.

Then, follow this route should be support:

/p1('8587bb44-ebe6-4db7-9532-7e7fa02ba36e')/p2
/p1('8587bb44-ebe6-4db7-9532-7e7fa02ba36e')/p2('some uuid')

[mauriceKA]

Thank you very much for your prompt reaction. Hope that my input helps a little making your library production-ready.