Комментарии:
Just a question here : in the example where he used the repository and the presenter, he had to use annotations in both of them. So, in a big project where we have more layers, we will have to put the annotations in all of them. Don't we suppose to avoid that to not make the code tightly coupled with a specific DI library ?
ОтветитьAmazing. I was already a koin fan but this is leap frogging the capabilities of Spring. One concern I have with ksp is getting locked into specific versions of Kotlin and not being able to upgrade when there are new releases of Kotlin. I've experienced this with other ksp based plugins. Basically not a problem if koin updates frequently but as soon as there is any lag with that, you are basically blocked on updating. It's a big reason, I'm avoiding ksp dependencies in most of my projects right now because I don't like being locked into a specific version of kotlin just because of some library I need. Any insight on how this would work with koin? Or whether in general this is something that can be solved?
ОтветитьLooks awesome!
ОтветитьDevex, hot reload would be super.
Ответить