New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide on a PATCH endpoint message format #88

Open

dotasek opened this issue Jul 27, 2018 · 2 comments

Contributor

dotasek commented Jul 27, 2018

PATCH endpoints would be useful for editing one or many resources, particularly visual properties.

Related RFCs:

https://tools.ietf.org/html/rfc5789
https://tools.ietf.org/html/rfc7396

GitHub makes use of the PATCH verb in it's own API, and could be useful as an example:

https://developer.github.com/v3/issues/#edit-an-issue
https://developer.github.com/v3/gists/#edit-a-gist

Contributor Author

dotasek commented Jul 27, 2018

Also The Google uses PATCH:

https://developers.google.com/drive/api/v2/reference/#Children

Contributor Author

dotasek commented Jul 27, 2018

https://developers.google.com/tasks/performance#patch

dotasek mentioned this issue

Add DELETE /v1/networks/{networkId}/views/{viewId}/{objectType}/{visualProperty}/bypass #93

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment