RequestSpecification.queryParam does not respect null values

[maxfd3v]

RequestSpecification.queryParam ("myParam", null)

Will be passed to the target API as a "" (Blank String)

One has to test the incoming parameter and skip adding a queryParam to make it work

[DeMol-EE]

Not sure what @maxfd3v expects to happen, but I for one would like it if the query param was simply skipped when the passed value is null. I realise that it’s possible to wrap adding the query param in an if with a null check, but it looks verbose, especially when used in a parametrized junit 5 test:

compare

        RequestSpecification req = RestAssured.given();
        if (foo != null) {
            req.queryParam("foo", foo);
        }
        if (bar != null) {
            req.queryParam("bar", bar);
        }
        Response res = req.get();

to

        RequestSpecification req = RestAssured.given()
            .queryParam("foo", foo)
            .queryParam("bar", bar);
        Response res = req.get();

I feel like it would be easy to draft a PR for this, but the problem is that it would be breaking, unless we add a new method, like optionalQueryParam?

[beng9re]

I opened a PR (#1776) to implement the functionality described in that part.

[injae-kim]

optionalQueryParam() will be so useful to many users include me :)