Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Implement support for IETF "application/json-patch" media type #1337

Closed
garysweaver opened this issue Sep 5, 2012 · 4 comments
Closed

Implement support for IETF "application/json-patch" media type #1337

garysweaver opened this issue Sep 5, 2012 · 4 comments

Comments

@garysweaver
Copy link

Please implement support for sending JSON patches with "application/json-patch" media type:
http://tools.ietf.org/html/draft-ietf-appsawg-json-patch-03

More discussion:
http://www.mnot.net/blog/2012/09/05/patch
http://news.ycombinator.com/item?id=4478627

Having a client that supports sending changes via standard JSON patch format would really help. Thanks!

@warpech
Copy link

warpech commented Sep 27, 2012

I am currently working on a directive that will add JSON Patch support to Angular JS. We will make it public once it is tested internally in my company.

I am not part of the Angular JS core dev team, we are aiming to release it as 3rd party directive.

@garysweaver, just to synchronize our effort, have you come up with something since you started this ticket?

@garysweaver
Copy link
Author

@warpech That's awesome! No, no progress on the AngularJS side. We use Rails service-side and had seen that Rails 4 had added PATCH method support and then @tenderlove wrote https://github.com/tenderlove/hana on the night of the the announcement about the spec (iirc), but on the Rails core list it sounded like adding support to Rails didn't fit in with their current direction. Looking forward to your contributions, though! Hopefully we'll be able to use them at some point.

@pkozlowski-opensource
Copy link
Member

There is a similar issue to default PATCH request to application/json

#899

@btford btford closed this as completed Aug 24, 2013
@btford
Copy link
Contributor

btford commented Aug 24, 2013

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants