You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving to DSL will help to ensure capacitor apps are supported for as long as possible.
I've been using it in a capacitor app in production for months now and it's been great.
I'm happy to do the work on this and PR the changes, but before I do, it would be good to know if it would be considered by the maintainers. It's not an insignificant change so I would understand if it's not up for consideration. From what I can see this would mostly be a change to the templates and making sure the migrations work fine. Is there anything else I'm missing?
Thanks
Alternatives
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Considering we are close to the final Capacitor 6 release and this kind of change would be a breaking change, I don't think it will be addressed short term, maybe for Capacitor 7. But adding the feature request label for tracking it internally.
Description
Move to Gradle DSL based build files for Android
Platforms
Request or proposed solution
Gradle DSL has been the default for new Android apps for some time now: https://developer.android.com/build/migrate-to-kotlin-dsl#timeline
Moving to DSL will help to ensure capacitor apps are supported for as long as possible.
I've been using it in a capacitor app in production for months now and it's been great.
I'm happy to do the work on this and PR the changes, but before I do, it would be good to know if it would be considered by the maintainers. It's not an insignificant change so I would understand if it's not up for consideration. From what I can see this would mostly be a change to the templates and making sure the migrations work fine. Is there anything else I'm missing?
Thanks
Alternatives
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: