How do you plan to support extensions of objects i...
# declarative-gradle
p
How do you plan to support extensions of objects in DCL? Without DCL, I have a top-level extension myExt provided by my base Gradle plugin, and some Gradle "sub" plugins adding an extension to the myExt like
myExt.feature1 {}
or
myExt.feature2 {}
. With KTS, there are generated accessors but AFAIK the DCL uses the static software type and not the dynamic extensions registered during runtime. Or should I create a new top level extension for each "sub" plugin?
a
As I understand, you cannot create one more top-level block in gradle.dcl and it is expected, it describes software type which specifies a type of the module As I remember it was mentioned here that some extension mechanics would be available, but not sure that it's the case on current prototype
In the future, additional types of software features will be added to Declarative Gradle to provide more capabilities to projects. For instance, the ability to add additional capabilities to a software type in a composable way, or the ability to restrict the model of a software type to a subset of its capabilities.
j
FYI. Composability/extensibility is one of the big objectives of the upcoming EAP3 for Declarative Gradle. Once that's out (planned for February), things should become clearer.
馃憤 2