Update/patch (PUT/PATCH) strips "id" from saved object

[jfexyz]

I'm still working on a test case, but I'm having issues with the update action. Not sure if it's in this module or another, but here are the details:

• Using custom id field (id, not _id)
• PUT /resources/123 with body {"id": "123", "title": "#123"} strips out the id field upon save.

This doesn't help, as it's not honored either; the id field is added to hook.data, but stripped again sometime before saving:

  service
    .before({
      update (hook) {
        // Copy ID from request into object.
        hook.data.id = hook.id
      }
  })

[jfexyz]

The same problem does not occur when PATCH is used, even when the id field is provided. However, if the id is changed in a PATCH request, it is not actually updated in the database (this is probably desired behavior).

The problem with the behavior in the PUT request is that the id is therefore stripped, so the resource becomes an orphan without an id.

[ekryski]

@joshuajabbour thanks for reporting! I released v2.1.1 that has your fix.

[jfexyz]

I've added comments on 5980ed6. While part the initial issue was fixed, I think the released fix introduces new bugs.