This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 64
Add the PATCH method for api/module/:name/authorization #246
Labels
Milestone
Comments
I've started looking at this, and discovered that we're using The question is: does the PUT method work like you want PATCH to work? Or is it overwriting values? |
@weierophinney the PUT works like a PATCH. For the new UI needs it's ok. I'm not sure that we want to support this behaviour, sounds quite strange for a PUT. |
We could deprecate PUT and have it return some warning in the payload, and then implement PATCH... and have it do what it's doing now. |
weierophinney
added a commit
to weierophinney/zf-apigility-admin
that referenced
this issue
Feb 2, 2015
Implemented PATCH as an HTTP method for the authorization service, and deprecated PUT.
weierophinney
added a commit
to weierophinney/zf-apigility-admin
that referenced
this issue
Feb 2, 2015
Implemented PATCH as an HTTP method for the authorization service, and deprecated PUT.
ezimuel
added a commit
that referenced
this issue
Feb 6, 2015
[#246] Authorization changes should occur with PATCH
steverhoades
pushed a commit
to steverhoades/zf-apigility-admin
that referenced
this issue
Mar 30, 2015
Implemented PATCH as an HTTP method for the authorization service, and deprecated PUT.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to support the PATCH for
api/module/:name/authorization
to add/update authorization for only one service. Right now, we have to PUT authorizations for all the services. This needs comes from the new UI that I'm implementing, I have specific pages per service.The text was updated successfully, but these errors were encountered: