This message was deleted.
# community-supports
Slackbot
04/08/2022, 5:51 PMThis message was deleted.
c
CristianGM
04/08/2022, 6:09 PMReading the docs I don't see the difference
CristianGM
04/08/2022, 6:11 PMI expected all to be "worst" (for example only consuming elements added before it's invoked) but it seems it's not:
Executes the given action against all objects in this collection, and any objects subsequently added to this collection.
e
ephemient
04/08/2022, 6:20 PM.allephemient
04/08/2022, 6:21 PMwhereas
.configureEachephemient
04/08/2022, 6:21 PMhttps://docs.gradle.org/current/userguide/task_configuration_avoidance.html#sec:old_vs_new_configuration_api_overview
Instead of:DomainObjectCollection.all(org.gradle.api.Action)
Use:DomainObjectCollection.configureEach(org.gradle.api.Action)
c
CristianGM
04/08/2022, 7:40 PMThat's what I expected...but then..maybe the docs need to mention it. 🤔
e
ephemient
04/08/2022, 7:43 PMit could probably be stated more clearly, but https://docs.gradle.org/current/javadoc/org/gradle/api/DomainObjectCollection.html
void all(Action<? super T> action)
Executes the given closure against all objects in this collection, and any objects subsequently added to this collection.
void configureEach​(Action<? super T> action)
Configures each element in this collection using the given action, as each element is required.already implies that configureEach is lazier than all
c
CristianGM
04/08/2022, 7:49 PMMeh, I would say it's unclear
e
Eli Graber
04/10/2022, 2:19 AMTook me a while to find this. It would be nice if there was something that would steer us towards the correct API to use. Maybe soft deprecating the existing eager APIs and providing a new one with clearer naming.
https://gradle-community.slack.com/archives/CAHSN3LDN/p1649442110194519?thread_ts=1649440291.522169&cid=CAHSN3LDN
e
ephemient
04/10/2022, 9:01 AMe
Eli Graber
04/11/2022, 2:15 PMWell now I feel stupid considering I already upvoted that issue 😆
5 Views