IssueTracker

My company uses the templating API extensively to generate boilerplate code activity, fragment, dagger etc. Removing the old system without providing documentation on the new system is at odds with promises made about improving the developer experience.

Hello all. Thanks for the feedback. We're definitely listening, and we understand that the change in behavior to the template system might have disrupted some of you.

Changing how we authored and processed templates was critical in moving the system forward. And, while we never officially supported custom templates, we understand that they played in important role in your day-to-day.

We're looking into how we can support it officially with the new Kotlin-based template system. But that will take some time, and we need to balance this work with competing priorities. We appreciate your patience and welcome more feedback that helps us create better tools for you.

There are issues far more urgent and important than this, and definitely no reason to insult other devs.

I also would like to have a templating API integrated with android studio but there are other ways of having a template and absolutely no excuse for being this mean.

In my last company, we did this via bash scripts. It's pretty reliable.

STOP THE "+1" COMMENTS

This is needlessly sending an email to every 180+ people following this issue.

Thank you for using the star button instead.

@comment#10: For all these people that relied on the previous template engine and have been broken after updating Android Studio to a newer version:

Is there a way to bring back that legacy in a way or another while the upcoming Kotlin-based is being designed and refined?

Hi everyone!

We at hh.ru created some kind of replacement for broken FreeMarker's templates. We've created a special Android Studio plugin, that wraps the current Templates API, and allows you to create templates and use your FTL-files -- we've called it Geminio. Here you can check out README for this plugin, and here -- you can download its distribution archive. For now, we support only Android Studio 4.1, but if you all will be interested in this plugin, we can add support for some other versions.

Also, we've written an article about this tool

Please, ask your questions in our repository, or on Medium, I will try to help you.

Hope this helps you all.

I am sorry removing of this feature caused so much inconvenience, but I want to notice that it was never supported officially and we never remove supported features in this way.

We are working on a replacement. It is taking so long because we want to make it great from the beginning, so we can avoid making backwards compatibility breaking changes in the future.

We will ship it as soon as possible. Very likely 2021H1, quite possibly next couple of months, but I can't give any guarantees.

Still not a proper replacement... but this article helped me get something useful in place instead of template apis

https://twitter.com/Terrell_6/status/1379701458245931009

Adding new project template could be a very convenient feature, hope it will be fixed soon.

claropay.com.citibanamex.transfer

• Cuenta clave 036180710048995487 E

Estadística

UJO DE FONDOS

GASTO INFORMES ÚLTIMOS 7 DIAS

CRÉDITO

Tabla de flujo de caja Necesito gráficos? :-)

Resumen rápido Ingresos Gast

OS

Cantidad

0

Promedio (Diario) Cuenta clave 036180710048995487 $1,490,371,608.14 $0 Promedio (Registro) $11,922,972,865.1 $0

.2

$0

Total $11,922,972,865.1-127320013778157783 cuenta clave banco azteca • 2

• Flujo de fondos $11,922,972,865.1

This is really frustrating. You don't offer Kotlin DSL templates and it is not possible to create custom templates. Both of these issues need to be alleviated.

Hello, I will explain my team's usecase with the templating API.

We are in the process of modularising the project and we would like to create our own module template. The current Android library module template creates quite a few files we don't want and makes changes we do not need such as adding the Android Kotlin plugin on the root build.gradle file.

I was looking into the .ftl way which I found out was no longer usable in favour of the new Kotlin DSL way. I was looking to implement such template basing it off source code seen here https://github.com/JetBrains/android/blob/9a7e4762e4fe381575172311b9f4fb4d87280fea/android/src/com/android/tools/idea/npw/module/recipes/commonModuleRecipe.kt . The biggest problem was actually creating the module itself as the current templates are activated off sub-projects and not the root project so the directories you get in fields such as moduleOut and srcOut are not correct. I couldn't find a way to retrieve the project instance and obtain root directory paths to create the module.

To summarise, it would be good if the templating API allowed us to make custom module templates.

Thank you