Unable to pass $data/unserialized parameter containing request body to method 'put' of custom rest resource plugin. This type of request is not considered in \Drupal\rest\RequestHandler::createArgumentResolver when preparing list of available arguments for argument resolver. I suppose it was not considered due to https://groups.drupal.org/node/284948.
Change condition from
if (in_array($request->getMethod(), ['PATCH', 'POST'], TRUE)) {
to
if (in_array($request->getMethod(), ['PATCH', 'POST', 'PUT'], TRUE)) {
As I see from https://groups.drupal.org/node/284948, PUT was put off because it adds problems for dealing with rest resources for entities. But there are cases when developers create rest resources not dealing with any entity. In this case the developers are fully responsible for logic of such resources including method 'put'. They probably don't face problems described in https://groups.drupal.org/node/284948 . So, I think we should allow such developers to implement proper REST API with support of PUT. Also, PUT is allowed by the rest resource base class. So, I think we should keep support of PUT on the basic level of rest resources since it was already done.
No
No
No
No
Fixed argument resolver for methods 'put' and 'delete' of REST resource plugins so, that now it provides request body to parameters with name $data or $unserialized.
Needs work
11.0 🔥
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Can the MR be updated for 10.1 please
Hiding files as the issue appears to be worked in the MR.
niels de ruijter → made their first commit to this issue’s fork.