[
https://issues.apache.org/jira/browse/GROOVY-10549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512637#comment-17512637
]
Christopher Smith commented on GROOVY-10549:
--------------------------------------------
Not on PropertyOptions unless you implement your own custom strategy class.
I did look at the various collected options before filing, and there's no
"JavaBeans compatibility flag" that I could see as of 4.0.1.
> Allow records to generate getter methods
> ----------------------------------------
>
> Key: GROOVY-10549
> URL: https://issues.apache.org/jira/browse/GROOVY-10549
> Project: Groovy
> Issue Type: Improvement
> Affects Versions: 4.0.1
> Reporter: Christopher Smith
> Priority: Major
>
> Records are very cool. However, the decision to drop the traditional
> JavaBeans prefixes means that _lots_ of infrastructure is incompatible until
> major libraries update to a baseline that includes record features. (For the
> moment, this includes the Groovy compiler...)
> For compatibility purposes, it would be convenient to still generate the
> traditional getFoo methods on records. This might not be preferable as a
> default, so perhaps it's a {{RecordOptions.getter}} setting?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
