Deserializing id back to _id

The serializer has the option to specify an alternate field as the id for a resource. This comes in handy when working with databases (notably MongoDB):

new Serializer("users", { id: "_id" }).serialize(users);

I wonder why the same facility isn’t available for deserialization so that after transport, the id can be properly mapped back to the appropriate field in the model:

new Deserializer({ id: "_id" }).deserialize(users);

[SeyZ]

I’ve added the support of the id option 😉 FYI, here’s the test:

  describe('id', function () {
    it('should override the id field', function (done) {
      var dataSet = {
        data: [{
          type: 'users',
          id: '54735750e16638ba1eee59cb',
          attributes: { 'first-name': 'Sandro', 'last-name': 'Munda' }
        }, {
          type: 'users',
          id: '5490143e69e49d0c8f9fc6bc',
          attributes: { 'first-name': 'Lawrence', 'last-name': 'Bennett' }
        }]
      };

      new JSONAPIDeserializer({
        id: '_id'
      }).deserialize(dataSet, function (err, json) {
        expect(json[0]).to.not.have.keys('id');
        expect(json[1]).to.not.have.keys('id');
        expect(json[0]._id).equal('54735750e16638ba1eee59cb');
        expect(json[1]._id).equal('5490143e69e49d0c8f9fc6bc');
        done(null, json);
      });

    });
  });

[prashaantt]

@jcw- FWIW, I worked around this by manually assigning _id to a new id attribute after deserialization, something like:

user.id = user._id;
delete user._id;

This is trivial to do but should ideally be built-in.