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

Gradle Community

interesting.  perhaps `providers.provider { collectionA.map { a-&gt; … }}` would suffice to make this lazy.

I don’t think that will work because I want to do the following later:

```domainObjectCollectionB
  .configureEach { b -&gt;
  }```
I could run the transform function (`(A) -&gt; B`) within a `.configureEach { }` - but I would have to duplicate calling that in multiple places, which is less than ideal

would something like `collectionA.whenObjectAdded { // add to collectionB }` work?

I have a type:

```// there are more properties, reduced for simplicity
data class MyModule(val gradlePath: String) // equivalent to project path```
I have a live `DomainObjectCollection&lt;MyModule&gt;` that I want to convert to `DomainObjectCollection&lt;String&gt;` (the `project.path`) and I need to keep the `MyModule` type around for other things

&gt; would something like `collectionA.whenObjectAdded { // add to collectionB }` work?
yeah this would probably work, not super clean though but may be my best bet

ok.  give `collectionA.whenObjectAdded { // add to collectionB }` a try.

the other option would be to look at why a separate collection is needed for the String/path - can that be simplified to be somehow derived e.g. provider).

I’m basically moving from a `Modules.ALL` statically defined global list to each subproject specifying it itself.

so I can move from `Modules.ALL: List&lt;MyModule&gt;` to `modules.all` (`modules` returns a gradle extension, `.all` is a live `DomainObjectCollection&lt;MyModule&gt;` that I use `.configureEach { }` to access)