Status Update
No update yet.
Comments
uc...@google.com
dw...@google.com
Jose, is this a duplicate of https://issuetracker.google.com/143291278 ? If so, should we close this one?
pa...@google.com
#2 This one is more global. https://issuetracker.google.com/143291278 addresses 1 of the 3 points of this ticket. I'll make this one dependent on the other, and assign it also to me.
David, for new Projects/Modules, do we have a plan how we are going to ask the user if they prefer build.gradle vs build.kts?
Is it a new check-box? Is it automatic, based on the "Kotlin" Language selection?
David, for new Projects/Modules, do we have a plan how we are going to ask the user if they prefer build.gradle vs build.kts?
Is it a new check-box? Is it automatic, based on the "Kotlin" Language selection?
pa...@google.com
Thanks again for helping testing this.
We fixed all the problems (we are aware) for breaking kts files (or re-create removed build.gradle). This should be on 4.0 Canary 5.
For offering the choice for new Modules and Projects to be in kts, we are in the phase of planning and should have more detailed tickets soon.
We fixed all the problems (we are aware) for breaking kts files (or re-create removed build.gradle). This should be on 4.0 Canary 5.
For offering the choice for new Modules and Projects to be in kts, we are in the phase of planning and should have more detailed tickets soon.
Description
It doesn't find settings.gradle.kts file too, so it creates a settings.gradle file and put there the new module and I have to manually delete it, and add manually the include to the kts file.
Should be great too if IntelliJ/Android Studio detects if exist a buildSrc folder so ask you for a custom implementation instead of create build.gradle files with a lot of things that you should to delete later. This is not a priority of course, but I think give fully support to kts should be mandatory.