Closed Shredder121 closed 9 years ago
I think this is at least a good place to edit this, since utils can be reused. But is it necessary to apply this elsewhere is what I mean.
@Shredder121 That's a good idea. Since there is also a constructor that takes both the class and the constant we can normalize the type in the constructor that takes only the constant.
@timowest also, the pom specifies a non-snapshot version. This pollutes my Maven cache..
I can bump the version to a SNAPSHOT after the next release. I applied the progress
label.
For simple interface implementations (anonymous classes) we could normalize the first interface. we could use a try block (since we move up the inheritance chain) and throw an exception when we reach Object, and go back down until we find a class that implements 1 interface, throwing an exception otherwise(moving further down).
This is just an idea (and not an optimal one). What do you think is a better one?
Or we could leave it at this. Maybe later, when we have a good test case we could implement that.
The current state of the fix might be sufficient for now. Shall I merge this?
Yes, I think that is good.
Shall we edit the commit message?
Yes, that makes sense.
I changed it now.
I'll make a new release for codegen tomorrow.
Released in codegen 0.6.6
progress
label needed.I haven't yet found a class that is not a descendant of
Map
,List
orSet
and has at least two non-visible parents. @timowest There may be a better way of going about this, it is maybe also solvable in querydsl-core in the creation of aConstantImpl
?