Open xlaussel opened 2 weeks ago
I think you should chek the
@Type
annotation prior to manage it as a Set.
Yes, i think this was the issue.
I made it check @Type
annotation first now instead of last.
ksp("com.github.IceBlizz6:querydsl-ksp:4698bab925")
Please try this build to see if it solves this issue.
I have an user defined type with Set as super:
I use it like that:
Leads to the following error:
[ksp] java.lang.IllegalStateException: Error processing MyEntity.mySet: Type looks like a set so expected 1 type arguments, but got 0
(It is just a simple reproduction of my case, I didn't test it but I am quite sure this will reproduce the bug)I think there are two bugs:
@Type
annotation prior to manage it as a Set. Anyway, there is no@OneToMany
or@ManyToMany
or@ElementCollection
, so why do you manage it as a collection? The truth comes from the Annotations! So there is a structural problem.