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

Gradle Community

actually, found;

```val collection: DomainObjectCollection&lt;MyClass&gt; = objects.domainObjectSet(MyClass::class)```

but I would still like to find a way to provide a custom “namer”

out of curiosity, why are you opposed to making a change to support this use-case?

I don’t want to couple `MyClass` to gradle API specific code. For the same effective reason extension functions are useful over instance functions

not to be difficult, but it's just unclear why you'd want a gradle-collection of something that wasn't already gradle-specific. Is `MyClass` also used for other build systems?

that said, I think you can just have a `name` property without implementing `Named`. So long as your class isn't `final`, Gradle will extend it at runtime

Tbh there’s no killer reason. Just want to have a clean separation of concerns. My new code to leverage `DomainNamedObjectCollection&lt;MyClass&gt;` is in one place - having to modify `MyClass` to support it is a bit messy

If you want such separation and class is not final you can just create subclass implementing `Named` and create named collection of these.