[GROOVY-10462] Groovy should not generate both `getFlag` and `isFlag` for a Boolean field.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 3.0.9
• Fix Version/s: 4.0.0-beta-1
• Component/s: Compiler
• Assignee: Eric Milles
• Reporter: Xiaoguang Wang
• Created: 21/Jan/22 03:50
• Updated: 28/Jul/22 15:23
• Resolved: 21/Jan/22 20:02

Description

Before, Groovy 2 only generates one getter for a Boolean field.

But now Groovy 3 generates two, it breaks some ORM frameworks (ex: MyBatis, it can not decide which getter to be used) and breaks JSON output.

And the meaning of `isFlag` is wrong, it should not return `Boolean` in my mind.

 

@CompileStatic
class Foo {

    Boolean flag

    static void main(String[] args) {
        Foo foo = new Foo()
        println(foo.getFlag())
        println(foo.isFlag())  // should not generate the `isFlag` getter
    }
}
 

Issue Links

• is related to: GROOVY-9382 Inconsistent support for [Bb]oolean properties
• is related to: GROOVY-10133 Inconsistent method selection for [Bb]oolean properties
• relates to: GROOVY-10707 Regression in property access for conflicting isXxx and getXxx accessors
• relates to: GROOVY-10708 Property access for wrapped vs. primitive boolean