From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I have no idea what is in the roadmap, but if any plugin needs an extension set to not fail application, that's imho a bug in that plugin, because that would also make it unusable (only ugly usable) within precompiled script plugins.

yeah, it doesn't compile so you can't get the autocomplete until you fill the minimum requirements of their extensions, but it is a usual pattern that I have seen in more plugins, so should be great that even when Gradle sync fails in IDEA, the accessors are still generated and allowing to use them and getting the autocomplete.

Again, any plugin that is not applicable via `plugins { ... }` block without any extension set is imho buggy.
This requirement makes them unusable (in convenient way) from precompiled Kotlin DSL script plugins.
Because the `plugins { ... }` block is extracted and applied to a dummy project to find out which accessors to generate.

Yeah, that implementation should be changed

Indeed, it shouldn't be necessary to do in that way, and it should be faster and more efficient using Fir if possible

I think those accessors are created and saved in `./gradle`, that wouldn't exist anymore, the plugin extension function can be generated with Fir in the project where it is needed, but I am not sure avoid how can be combined Fir with kts files and how it is already implemented the kotlin compiler in the embedded Gradle ones.

At the end I have only played with Fir in "normal" kt files

a compiler plugin doesn't make sense to me - this is purely an IDE feature

looks like there will be compiler plugins with Fir support for scripting too, not soon tho

why IDE feature? using the frontend compiler should be faster and at the end it is kotlin code