Patch is deleting subdocument data

My API uses feathers-mongoose for the db and when I send JSON (via postman) to patch my model I’m losing subdocument (embedded?) data. For example, if I have a model like this

social: {
        facebook: {
            url: String,
            likes: Number
        },
        twitter: {
            username: String,
            followers: Number
        }
}

and I send a patch request with

{
    "social": {
        "twitter": {
            "username": "@the_username"
        }
    }
}

it deletes social.facebook

Expected behavior

It shouldn’t delete the sibling subdocuments. In this example social.facebook.

System configuration

Module versions (especially the part that’s not working): feathers-mongoose@3.5.3

NodeJS version: v6.5.0

[daffl]

I think this has been figured out right? I think in general Feathers should leave the deep-merge behaviour up to the ORM since some (like all SQL ORMs) don’t even support nested objects at all.

[imns]

I agree about using $set. This issue (https://github.com/feathersjs/feathers/issues/323) mentions that $set is being used, but I don’t see that anywhere.

@corymsmith I am not using feathers client. I’m sending a patch request directly to the API.

Update

I just tried sending { $set: { "social.twitter": {username: '@the_username'} } } with postman and it worked.

This seems counterintuitive since a patch request by nature needs to use $set.

Update2

$set seems to want dot notation. This works

"$set": { 
        "social.twitter.username": "@test"
    }