API v1.1 - json-patch

Registered by Kurt Griffiths on 2014-08-01

OK, we need to avoid scope creep for v1.1, but now that json-patch RFC is pretty stable, should we add PATCH support for queue metadata, and also make patching claims and pools use json-patch?

http://jsonpatch.com/

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Kurt Griffiths
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Feilong Wang on 2016-06-23
Completed by
Feilong Wang on 2016-06-23

Related branches

Sprints

Whiteboard

We have done this for v2 queue and need to do this for the other services. But will follow up with separated bp.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.