Support @Validated validation groups

Is your feature request related to a problem? Please describe. Using one request object for PUT and PATCH methods and using @Validated annotation with validation groups should respect the validation of the group.

import org.springframework.validation.annotation.Validated;
import org.springframework.web.bind.annotation.PatchMapping;
import org.springframework.web.bind.annotation.PutMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("controller")
public class Controller {
  @PutMapping
  public void put(@RequestBody @Validated(Request.PUT.class) Request request) {}

  @PatchMapping
  public void patch(@RequestBody @Validated(Request.PATCH.class) Request request) {}
}

import javax.validation.constraints.NotNull;


public class Request {
  @NotNull(groups = {PUT.class}) public String name;

  interface PUT {}

  interface PATCH {}
}

Generates: irrelevant parts omitted for brevity

{
    "openapi": "3.0.1",
    "info": {},
    "servers": [],
    "paths": {
        "/controller": {
            "put": {
                "tags": [
                    "controller"
                ],
                "operationId": "put",
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "$ref": "#/components/schemas/Request"
                            }
                        }
                    }
                },
                "responses": {}
            },
            "patch": {
                "tags": [
                    "controller"
                ],
                "operationId": "patch",
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "$ref": "#/components/schemas/Request"
                            }
                        }
                    }
                },
                "responses": {}
            }
        }
    },
    "components": {
        "schemas": {
            "Request": {
                "required": [
                    "name"
                ],
                "type": "object",
                "properties": {
                    "name": {
                        "type": "string"
                    }
                }
            }
        }
    }
}

Describe the solution you’d like In the above example the patch route should have name as an optional parameter, not required

Something like:

{
    "openapi": "3.0.1",
    "info": {},
    "servers": [],
    "paths": {
        "/controller": {
            "put": {
                "tags": [
                    "controller"
                ],
                "operationId": "put",
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "$ref": "#/components/schemas/Request_PUT"
                            }
                        }
                    }
                },
                "responses": {}
            },
            "patch": {
                "tags": [
                    "controller"
                ],
                "operationId": "patch",
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "$ref": "#/components/schemas/Request_PATCH"
                            }
                        }
                    }
                },
                "responses": {}
            }
        }
    },
    "components": {
        "schemas": {
            "Request_PUT": {
                "required": [
                    "name"
                ],
                "type": "object",
                "properties": {
                    "name": {
                        "type": "string"
                    }
                }
            },
            "Request_PATCH": {
                "type": "object",
                "properties": {
                    "name": {
                        "type": "string"
                    }
                }
            }
        }
    }
}

Describe alternatives you’ve considered Obvious alternative is different request objects. Though this is annoyingly verbose for the above case.

[omarAbdelhadyok]

Can you provide an example on how to achieve this using @RequestBody or @Parameter?

[Showleen]

plan support it?