-
Notifications
You must be signed in to change notification settings - Fork 639
Closed
Labels
staleStale issues which are marked for closureStale issues which are marked for closure
Description
Hey!
First of all, thanks for a great library!
This is just a suggestion and I wanted to know what you guys thought about it. Feel free to close it, if it does not make sense.
I noticed that all the gradle files are in Groovy, what do you guys think about converting it to Kotlin DSL? Is there a reason for not migrating or any downside to migrating? :)
I would love to help out and contribute if this is okay :)
One suggested approach to this as we did when migrating in the horologist project is the following:
- Go module by module prepare the Groovy scripts following the steps described here. Then make a PR for each module to keep it easy to review.
- Do the actual conversion of the file to
.kts
and check that it compiles and that everything works as expected. Then make a PR for each module, to make it easy to review.
One tool that might help migrate is this script to convert Groovy to Kotlin DSL. I have not tried it myself though.
Metadata
Metadata
Assignees
Labels
staleStale issues which are marked for closureStale issues which are marked for closure