I had a getX and setX as GET and POST operations a...
# intellij
p
I had a getX and setX as GET and POST operations and it detected them as a val with custom getter and setter
a
yes, kotlin resolves methods called
getX
as getters of
x
p
I understand it, but in some cases it shouldn't do it, maybe the converter should have some extra checks like looking if the methods are annotated with certain "blacklisted" annotations, or only accepting "whitelisted" ones
a
@Pere Casafont you can still use
getX
as usual
c
This annoys the hell out of me when converting Spring MVC controllers or jax-rs resources from Java to Kotlin...
p
this is what I mean, it's just an annoying artifact of the convertor and I was suggesting improvements to prevent it from happening