I've converted several codebases from Java to Kotlin including one I'd consider to be a "larger" Android app on the scale of Collect. I do! I'm guessing has noticed from my not so subtle "well in Kotlin."s during our discussions.įor context on where I'm coming from on this: I've been working in Kotlin since before it's 1.0 release and have been using it in production across Android and web (mostly Spring) since the beginning of 2016.
i would really appreciate any feedback regarding this proposal Sorry for my lack of knowledge (i am still learning). I just recently joined the company so i am not totally aware of all the problems the team faced while migrating. I know my answer is lacking all the details you were expecting. So we left that part untouched for now.Īs For the strategy we followed we were using mvvm architecture so we started from the entity layer and moved higher in the hierarchy and most of the migration can be easily done with java to kotlin tool in android studio our work was mostly to lookout for errors in generated code and correct it. another case is few Unit tests and java fields were broken due of NPE(Null Pointer exception) in kotlinģ.a Third party lib(in our case one of payment gateway lib) was creating a lot of problems. it was only a minor change as we were able to correct it with help of error messages.Ģ.
I guess one of the problem was with using lateinit keyword in kotlin code. when we ported the code to kotlin we faced few problems.ġ.The first problem was with Dependency Injection (Dagger 2). Ok i got it.Actually i am working in a online movie booking app(JusTickets).
0 kommentar(er)
