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

Gradle Community

I launched our first <https://github.com/Hinge/project-accessors|Gradle plugin>. We use an internal Gradle API (namely `ProjectDependencyInternal`) to emulate what typesafe project accessors. I understand this is risky but feel the risk is worth it in this case, but of course I'd prefer to not use the internal API. Is there any other way around this with today's API that doesn't require extra syntax?

What I mean by "extra syntax" is having to write `.dependency` or `projectDependency(...)` or something else that resolves get a `ProjectDependency` from the generated accessor.

I'm not sure I understand the benefit of making a new type for each project accessor, why not just have those be ProjectDependency?

Because I need to generate nested accessors, just like the standard gradle accessors:
```project.foo.bar.baz```
So if `project.foo` returned a `ProjectDependency` I couldn't expose `bar`