Creating a custom resource with PUT or PATCH method

I'm able to use it with GET/POST/PATCH requests (the ParamConverterInterface code it's being executed) but not for PUT requests. It seems that the converter doesn't get processed on this request methods.

If I log in convert method the "array $defaults" parameter I see that Route object has this:

[methods:Symfony\Component\Routing\Route:private] => Array
(
[0] => GET
[1] => POST
)

[requirements:Symfony\Component\Routing\Route:private] => Array
(
[_method] => GET|POST
)

I have added in routing.yml for my custom route:

requirements:
_method: GET|POST|PUT|PATCH|DELETE

And now I see it like this:

[methods:Symfony\Component\Routing\Route:private] => Array
(
[0] => GET
[1] => POST
[2] => PUT
[3] => PATCH
[4] => DELETE
)

[requirements:Symfony\Component\Routing\Route:private] => Array
(
[_method] => GET|POST|PUT|PATCH|DELETE
)

But still doesn't get processed for PUT requests. Only for the other four.

Also, how can I read request data (body parameters) for PUT/PATCH requests in order to build my custom object class?

Thanks.

What is "array $data"??? In ParamConverterInterface there is an "array $defaults" only.

But you have said that I need to create a ParamConverterInterface. If I do this reading documentation I see that I need to create an entry on "*.routing.yml" defining it like this:

my_id:
path: '/api/device/{device_id}'
requirements:
_method: PATCH
options:
parameters:
device_id:
type: device

Create a Converter:

class DeviceConverter implements ParamConverterInterface {

  public function convert($value, $definition, $name, array $defaults) {
    return $data; // here I return my data class
  }

  public function applies($definition, $name, Route $route) {
    return (!empty($definition['type']) && $definition['type'] == 'device');
  }

}

Reference it in "*.services.yml":

device_converter:
class: Drupal\my_namespace\DeviceConverter
tags:
- { name: paramconverter }
lazy: true

I only want to convert that "device/{device_id}" to an object reading PATCH request body data to a custom object. I see that using paramconverts it's the way but if I don't see a complete example (It has been impossible to find one and I have searched Drupal source code).

But If I don't need to create a route how it's going to use my ParamConverter??? I need to tell somewhere that it needs to use it.

Also I don't understand this:

function post(array $data) {

I don't want that. You said that creating a ParamConverter I can receive as parameter my converter object (using a ParamConverter) directly, like this:

function post(Device $data) {

Also take in mind that I need it to PUT/PATCH not POST.

/colgate/api/device/{device_id}

I'm requesting it like this:

PATCH http://{host}/api/device/a921ebdd9d10f21602d949fc6edd6154280c590e?_format=json HTTP/1.1
Content-Type: application/json
Accept: application/json
X-CSRF-Token: c3o_rUqq9GHAdK9nXLb0g7YCpv8VY-SCt2QDtJPg95o

{"deviceId":"a921ebdd9d10f21602d949fc6edd6154280c590e","registrationId":"1234","platform":"android"}

And I want that JSON data to be serialized to a Device object and it's why I'm using a ParamConverter like you said to have a result like this:

function patch(Device $data) {
echo $data->deviceId;
echo $data->registrationId;
echo $data->platform;
}

What you want to achieve is totally reasonable. I can also see how it's simply too hard to do today. I'll work on adding test coverage that A) proves it's possible, and B) serves as an example. And in doing so, I should run into all the problems you're running into — it's quite likely there's several bugs hiding there!

Thanks! I'm looking forward to that example.