-
Notifications
You must be signed in to change notification settings - Fork 828
Adding Kotlin Support #2357
Comments
@sriramr98 I think you can go ahead with converting one Pojo to Kotlin and we can review that and merge. |
I think we should start with converting utility classes instead of a Pojo. There are some small issues with data classes and Realm that needs to be fixed before converting a Pojo. So I think we should start with some Utility Classes. |
@the-dagger Sounds good, And I agree, utility classes should be converted first as the data layer s already being reworked in this library https://github.com/iamareebjamal/openevent-java |
So I will start converting two-two utility classes at a time |
@sriramr98 Would you like to split up? |
@mayank8318 I'm sorry man, I'm trying to include this as a small part of my GSoC proposal. If I don't get selected for it, then we can split up the work, collab and get the job done. |
The PR does not solve this issue as this issue will be closed when entire project is completely converted to kotlin |
@iamareebjamal Can we continue with this issue? Should we start with some util classes or start refactoring activities? |
Util classes first |
Alright. Ill push two util classes a day and we'll see how it goes. |
@iamareebjamal the utility classes have been converted. What next? |
Convert non android specific classes |
Steps to reproduce it
Kotlin is an awesome language that introduces verbosity and conciseness for the project. Adding Kotlin support to the project will improve the quality of the code with significantly reduced codebase. I would like to start by adding kotlin in incremental builds - one fragment at a time.
Would you like to work on the issue?
Yes. I would like to work on this issue
Target Milestone to solve the issue
I would like to take this up for GSOC 2018 as a milestone.
The text was updated successfully, but these errors were encountered: