Query with null value included

[dip-dev-info]

In the last release 5.0.1 in query, the value is null - URL request was configurated with an empty value.

/categories?offset=&limit=

In the previous release, 5.0.0, these queries were not included.

/categories

Example:

@Get(path: 'categories')
  Future<Response<DtoPagination<DtoCategory>>> categories(
    @Header('Request-Service-Location') String service, {
    @Query('offset') int? offset,
    @Query('limit') int? limit,
  });

[techouse]

That is by design #364 as most if not all backends ignore it anyway. The previous way of truncating it was wrong.

[dip-dev-info]

Ok, but Laravel (PHP) don't ignore it.
It perceives as an empty text (string - ""), but the number (integer) is required - an exception occurs.
So, this method is also not entirely correct and is redundant - data is transmitted that can only sometimes be useful.

It would be correct to add a key to the annotation that is responsible for ignoring or not such data.
But if it is difficult to do this through the annotation, then you can add it to the chopper settings

[techouse]

I could add an annotation to @Method to truncate null query parameters, yes.

[techouse]

Check #372