-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarkus Rest empty @QueryParam is handled differently #44885
Comments
It seems the change is not in validation but in how the empty query param is treated I have another failing test on a similar case where |
THis started to fail on Nov 18 and was working on Nov 15 |
here is a new reproducer clearly showing that empty query params are now handled differently: |
/cc @FroMage (rest), @stuartwdouglas (rest) |
This change was intentional, and explained in #42468 (comment) If you have use-cases that require the old behaviour, let us know, because we could not think of any. |
Thanks for spotting that @FroMage! I had completely forgot about that one... |
@FroMage let's close this when this is in the migraition guide |
Thanks @FroMage @geoand @cescoffier |
Describe the bug
I initially discovered this in code.quarkus unit tests. For example when using
?a=
with a a List, the list size is not 0 while it was 1 before (with""
) as content.Same with String, before it was an empty string, not it's not defined.
Expected behavior
not sure but we need to clarify if it's an expected change
Actual behavior
it assumes
?a=
is the same as?
How to Reproduce?
reproducer-validation.zip
This reproducer works on 3.17
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
main (3.18)
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: