should change add to replace?

when I run the follow case with python-json-patch, it failed. Detail in stefankoegl/python-json-patch#111 (comment). But when I change the add operation to replace, it succeeded.

json-patch-tests/tests.json

Lines 63 to 66 in ea3af85

    
           { "comment": "replace array document with object document?", 
        
             "doc": [], 
        
             "patch": [{"op": "add", "path": "", "value": {}}], 
        
             "expected": {} },

A path of "" means the root, or whole document.
See https://datatracker.ietf.org/doc/html/rfc6901#section-5

"" // the whole document

The fact "add" to the whole document does a replace is covered by this part of the json-patch spec

https://datatracker.ietf.org/doc/html/rfc6902/#section-4.1

If the target location specifies an object member that does exist, that member's value is replaced.

The root exists, so it becomes a replace op

Navigation Menu

Repository navigation

should change `add` to `replace`? #44

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	{ "comment": "replace array document with object document?",
	"doc": [],
	"patch": [{"op": "add", "path": "", "value": {}}],
	"expected": {} },

should change add to replace? #44

Description

Activity

jayvdb commented on Aug 15, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

should change `add` to `replace`? #44