[GROOVY-5243] @Canonical @TupleConstructor can't handle Object or Map properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.5
• Fix Version/s: 2.1.3, 2.2.0-beta-1
• Labels: annotation
• Assignee: Paul King
• Reporter: Grégory Joseph
• Created: 09/Jan/12 05:08
• Updated: 25/Oct/22 16:49
• Resolved: 12/Apr/13 04:05

Description

Given the following code, I would expect the assertions to pass. They currently don't. However, if the a and b properties are typed to String, for example, everything goes as expected.

It might be challenging to get this to work properly for more complex types, but it would make the annotations really transparent. The way it currently behaves is very unsettling (a is set with a Map containing both a and b with their respective values, while b is not set to anything)

import groovy.transform.Canonical

def weird = new CanonicalIsWeird(a: 'first letter', b: 'second letter')
println "a: ${weird.a}"
println "b: ${weird.b}"

assert weird.a == 'first letter'
assert weird.b == 'second letter'

@Canonical
class CanonicalIsWeird {
    def a, b
}

https://gist.github.com/1565938

Issue Links

• is part of: GROOVY-10796 TupleConstructor and map-ish constructor style don't mix