Failed validation of query param returns empty field in violations list

[lwitkowski]

Describe the bug
Failed validation of primitive input returns empty 'field' in violations list

To Reproduce
Endpoint:

@GET
@Path("/search")
public String search(@QueryParam("phrase") @Length(min = 10) String phrase) {
    return "not relevant";
}

Request:

curl http://localhost:8080/search?phrase=abc

Response:

{
    (...)
    "violations": [
        {
            "field": "",
            "message": "length must be between 10 and 2147483647"
        }
    ]
}

Expected behavior
field in violation object should be phrase instead of empty string

{
    (...)
    "violations": [
        {
            "field": "phrase",
            "message": "length must be between 10 and 2147483647"
        }
    ]
}

[amasnik]

After some internal discussions we came up with new structure which is no longer a bug but an enhancement

Endpoint example:

    @GET
    @Path("/constraint-violation-exception-mix/{phrase_name}")
    public void throwConstraintViolationException(@Valid @QueryParam("phrase_name") @Length(min = 10, max = 15) String phraseName,
                                                   @Valid @PathParam("phrase_name") @Length(min = 10, max = 15) String phraseName2,
                                                   @Valid TestRequestBody payloadBody) {
    }

    public static final class TestRequestBody {
        @Min(15)
        public int phraseName;
    }

Expected output

"violations": [
            {
                "field": "phrase_name",
                "message": "...",
                "in": "query"
            },
            {
                "field": "phrase_name",
                "message": "..."
                "in": "path"
            },
            {
                "field": "phraseName",
                "message": "..."
                "in": "body"
            }
        ]

[lwitkowski]

Enhancement extracted to #102 , let's keep it as bug :)