In reference to http://drupal.org/node/1099508, which is old and closed, I'd like to propose the opposite: to remove actions. The problem with actions is that it prevents me from creating POSTing to create a subordinate, as in (POST) endpoint/comment/1, to create a reply to the identified comment.

For the purpose of not breaking legacy RPC-like implementations, I think a fallback behavior could be implemented such that if no known action is named then we treat the resource as a collection and create the subordinate. Thus,

(POST) endpoint/comment/123/publish would work as it always did but (POST) endpoint/comment/123 would create a reply on cid 123.

As an aside, the above mentioned issue included a comment about removing targeted actions. I like the targeted actions, since they allow things like (DELETE) /user/1/session.

Comments

ygerasimov’s picture

ygerasimov commented
Status: Active » Fixed


(POST) endpoint/comment/123/publish would work as it always did but (POST) endpoint/comment/123 would create a reply on cid 123.

For this case I believe you should be able to implement "create" method that has path argument. And there you can create reply to the comment 123.

Or you can implement endpoint/comment/123/reply targeted action that will work nicely as well.

Regarding #1099508: Remove relationships and targeted actions I completely understand now why actions and targeted actions were done and understand why they are really needed. So no need to remove anything.

Please feel free to reopen this issue if you have any questions.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.