Does anyone know if it is possible to define a specific glue validation yaml for versioned endpoints? Lets say we have a resource called: my-resource. We have a validation file that is as follows:

my-resource:
  post:
    name:
     - NotBlank

Now we have a version for this resource: /v2.0/my-resource And we want to have a new property phone required only for this version Is this possible in any way with the validation yamls? Thanks in advance

Hey, sorry, as far as i know this is not possible right now 😕

Thank you!

A colleague of mine just asked to clarify which approach was used to create versioned API?

Using the

ResourceVersionableInterface

in the ResourceRoutePlugin