-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Fix primitive class handling in Serialisers #37788
Conversation
geoand
commented
Dec 16, 2023
•
edited
Loading
edited
- Fixes: #Rest client does not support other primitive response types when filter like OIDC client filter is used after optimization of primitive checks #37776
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer this one as well!!! Thanks @geoand
🙏 |
@@ -18,7 +18,7 @@ public class ResponseInfoResource { | |||
|
|||
@Path("/simple") | |||
@GET | |||
public String get(@QueryParam("abs") String abs) { | |||
public boolean get(@QueryParam("abs") String abs) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a test instead of changing an existing one?
Or this is safe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's totally safe because the response itself was not being used anywhere and now it is.
I also checked that with this test the previous version of the code was failing
@geoand please check if there was some useless private empty method which was used in the Serialisers https://github.com/quarkusio/quarkus/pull/37778/files#diff-4331c4565452796771e5f021cc452593f1cbb4ee69557f63868aae37641769c6L263 |
There don't seem to be any |
I am surprised...the diff I have posted was with my change that was removing that dangerous used empty method (and replacing the usages with the right one)...where is gone? ... minutes later ... Found it! Line 123 in 7f3dfb8
So it should be declared there and replaced with the one you have added If we had no failures despite it we are lacking some tests |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've checked and this fixes my issue.
@franz1981 thanks! Fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Would it be possible to get it in, please? |
ah, I didn't mention of this, okay let's wait, just annoying to have CI failures |
Yeah, let's wait for a review from @gsmet |
Sorry for the delay! |
🙏 |