QueryDSL bindings treat empty parameters inconsistently [DATACMNS-1784]

[spring-projects-issues]

James Howe opened DATACMNS-1784 and commented

The MVC binding treats empty request parameters inconsistently.

A single empty parameter will be ignored, but if there are multiple then they are passed as null (or "" for String types, [] for arrays).

• ?foo= — no binding created
• ?foo=1— one value: [1]
• ?foo=1&foo= — two values: [1, null]
• ?foo=&foo= — two values: [null, null]

This leads to inconsistent behaviour, including NPEs in QuerydslBinderCustomizer and such

---

Affects: 2.3.2 (Neumann SR2)

[spring-projects-issues]

Mark Paluch commented

We should address the NPE's right now and let's aim to make the behavior consistent with Spring Data 3.0