:wave: Hey all i've noticed this cool feature `TYPESAFE_PROJECT_ACCESSORS`which is in experimental ...

# gradle

[prudhvi reddy]

👋 Hey all

i've noticed this cool feature `TYPESAFE_PROJECT_ACCESSORS`which is in experimental from Gradle 7.0

Are there any downsides in enabling this?

Is team considering to move this feature to stable sometime?

[Hristijan]

been using it since the day 1 when they’ve announced it as experimental without any problems, maybe they just forgot about it hahaha 😄

[prudhvi reddy]

Just checking if there is any cost in using this in big scale projects

Otherwise, i don't see why this shouldn't be in full rollout.

[tapchicoma]

AFAIK the root project accessor ambiguity is the main reason it is still experimental. Otherwise it should stay

[hfhbd]

There are still some edge cases, like naming a project extensions but besides that, test it out. I use it in all my projects and I don’t expect any changes.

[mbonnin]

I've had some issues with them a long time ago, not sure if it's the case anymore but I generally try to stay clear of them. I don't mind the missing type safety too much as typos are usually detected early enough.

[Oleg Nenashev]

Hi. Thanks for bringing it up. I assume this API is generally under a bigger umbrella of the Provider API, but not 100% sure

[prudhvi reddy]

@Oleg Nenashev Just noticed the channel description, Should i move this post this message in gradle community?

[Oleg Nenashev]

It would be better. Though, maybe, we should rather split the Gradle channel to #gradle-for-kotlin and #gradle-misc if the admins agree. CC @Alina Dolgikh [JB]

[mbonnin]

Maybe even #kotlin-gradle-plugin ? Like generic Kotlin DSL questions are probably better in the Gradle slack I think? (or at least it's how I have been using this channel)

[Alina Dolgikh [JB]]

I don't have objections

[ritesh]

We have it enabled for our project, didn't notice any issue so far.

[ritesh]

I would keep an eye on warnings, especially if you are working in a project with composite builds. I am not sure, if it got fixed but we had to add the rootProject.name for all builds to avoid breaking caching.