Need to consider whether types with subattributes should show attributes that are "null" or not

[justingaylor]

When rendering types with subattributes, we need to decide whether subattributes that are nil should be returned or not.

We currently return them:

{
  "timestamps": {
    "created_at": "2014-11-20T20:41:12+00:00",
    "updated_at": "2014-11-20T20:43:22+00:00",
    "deleted_at": null
  }
}

[careo]

I hit a number of other... quirks... with nil subattributes with the praxis plugins as well. So there's definitely some tweaking needed around them.

[shaley91]

I have already spoken to @justingaylor and @careo about an issue when using attributor with PATCH calls.

For Example
We have an update call that uses PATCH instead of PUT.

So for example if I have a resource called User which has the attributes:

============
name: String
email: String

If I wanted to just update the name I could call PATCH /user/:id, { name: 'updated_name' } and leave out the email attribute.
But what happens is that attributor/praxis detect that the email isn't there and add it to the payload.
So the request comes through like this: { name: 'updated_name', email: nil }.