:kodee_loading: Following yesterday’s discussion o...
# spring
t
kodee loading Following yesterday’s discussion on the advantages of Kotlin over Java with Spring. What do you feel is missing in Kotlin + Spring tooling support in IDEA these days, what could be better?
r
a minor inconvenience for me: in my projects I am using the kotlin-spring compiler plugin to make sure that my Spring-annotated classes are automatically
open
. However, sometimes I have classes that are not annotated with any Spring annotation, but instead they are exposed as a Spring bean in a
@Configuration
class. In that case I have to manually make the class
open
, otherwise Spring will use some nasty proxying to do any aspect-related things happening in the class (e.g. to support an
@Cacheable
or
@Transactional
annotated function), which in turn can lead to some weird errors. It might be nice if the IDE warns me for this, indicating that a class is used in a bean configuration, but it (or its public functions) is not open for extension?
👍 4
👍🏾 1
w
my main complaint is that when i use functional spring interfaces like beans dsl and context initializers, intellij does not know what beans exist so i get a lot of red squigglies. I develop a framework that uses these APIs, and if there was a way to have my framework output a file at build time that could inform the tooling about which beans exist id be very interested in that, but i have not been able to find any docs around this
👍 1
p
Error on suspend functions with Spring AOP annotations 🤔 that nasty continuation object mess up that but ofc there are no warnings no errors it just doesn’t take place. It would be great if IDEA could identify these and gave us a heads up that it will not work
👍 1
j
What's with kapt? Is it deprecated? Is spring migrating away from it?
1