This message was deleted.

Did you hit some limitation? I'm not aware of any docs about it. But I would either assume there is no restriction, but then the convenient accessors might not work, or the restriction to be identifier names so that the accessors work. But if I were to guess, then the former.

I was adding objects that were named by the the file path, so

/path/to/some-file.txt

, and I was wondering if that would be a problem. I ended up converting the paths to camelCase so that the generated accessors were pretty, but perhaps that’s not necessary?

TIAS :-D

TIAS?

Try it and see

ahhh

AFAIK there are no restrictions on namers but typed accessors are only generated for legal Kotlin names

Without testing I would say illegal Kotlin names are just escaped, like the plugin ids.

https://github.com/gradle/gradle/blob/master/subprojects/kotlin-dsl/src/main/kotlin/org/gradle/kotlin/dsl/accessors/CodeGenerator.kt#L296 they're just skipped

For tasks it complains:

The task name '/path/to/some-file.txt' must not contain any of the following characters: [/, \, :, <, >, ", ?, *, |].

yeah that seems to be added in https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/java/org/gradle/api/internal/AbstractValidatingNamedDomainObjectContainer.java which is a parent of many common collections but not custom ones

"many" as in "four" 🙂

name filter also permits ``` which isn't a legal Kotlin identifier part, so it's still possible for a generated accessor to not work