Re: [apps-discuss] draft-snell-merge-patch-08 in Ruby

I may need to take another pass at explaining this in the draft.
Essentially the idea is this: In the PATCH document, a null always
means that the key or element must not appear in the final result.

Given James M's example cases, the results should be:

> Document + patch = ?

> [1,2]  +  {"a":"foo","b":null}

  Result: {"a":"foo"}

> {"a":"foo"}  +  {"b":[3,null,{"x":null}]}

  Result: {"a":"foo", "b":[3,{}]}

> {"a":"foo"}  +  null

  Result: Invalid. The patch document MUST be a valid JSON document,
which means the root must be either a JSON object or array. A null
patch document is invalid.

If there is an error in the javascript impl in the draft, I'll make
sure that gets corrected in the next iteration.

- James

On Sun, May 19, 2013 at 9:00 PM, Steve Klabnik <steve@steveklabnik.com> wrote:
[snip]
>
>> Why both removing array elements that are null (obj.compact)?
>
> I took that to be what this meant:
>
>        Any
>        object member contained in the provided data whose value is
>        explicitly null is to be treated as if the member was undefined.
>
> Since 'null' means 'remove' as the value of a key, I just assumed all
> nulls should be removed. I did find this sentence (which is
> everywhere) a tad bit confusing.
>
> This could be me mis-reading things.
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss