-
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
Support for short and uncommon field names like set, get, and is #44457
Conversation
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
/cc @mariofusco |
@@ -281,7 +281,7 @@ private Type fieldType() { | |||
if (isPublicField()) { | |||
return fieldInfo.type(); | |||
} | |||
if (methodInfo.name().startsWith("set")) { | |||
if (methodInfo.parametersCount() == 1 && methodInfo.name().startsWith("set")) { |
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.
👍
...ain/java/io/quarkus/resteasy/reactive/jackson/deployment/processor/JacksonCodeGenerator.java
Outdated
Show resolved
Hide resolved
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.
@burl21 Thanks a lot for this fix, I'd just prefer to keep it more confined to the "set", "get" and "is" field name it is supposed to support, so please see my suggestion.
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 rebased and squashed the commits. Let's wait for CI and merge!
Thanks!
Status for workflow
|
Merged, thanks for your contribution. The fix will land in 3.16.4 that we will release next week. |
fix: #44433
Enhance handling of short field names specifically for records, ensuring correct support for fields like set, get, and is.