This message was deleted.
# community-support
s
This message was deleted.
v
What's the use-case? Or more specifically, why do you not use a task? Sounds like having the semantics you want.
c
the use case is stupid people... esp me. when someone first uses the repo, and even when the IDE (ideally) first consumes the repo, it should run code instead of telling a human to do it
and if for some reason that code should (rarely) become stale
it could easily get re generated
this is stuff like properly pointing
git.core.hooksPath
sure I can document doing it
or I could just... have it happen whenever you tried to do anything
c
Perhaps something like this:
Copy code
tasks.withType<Task>().configureEach { 
    dependsOn(myCustomInit)
}
…then bake what you need into the custom tasks
myCustomInit
, handling inputs/outputs to get up-to-date checking.
v
That was about what my suggestion would have been, except for the needless
withType
, just
tasks.configureEach { dependsOn(myCustomInit) }
👍 1
Or if you do the up-to-date stuff yourself, just do it in the configuration phase.