Dependency Injection generated files

[nizam-betterapp]

We use ksp plugins in our android project to do some dagger hilt annotations. When doing gradle build, it creates file under this directory for an app with package name com.example.blah

~/project_dir/app/build/generated/ksp/debug/kotlin/com/example/blah/destinations/MyGeneratedFile.kt
We import it as import com.example.blah.destinations.MyGeneratedFile

I want language server to index these files as well so that "Go to definition" kind shortcuts work.
Please help.

P.S: I have tried various IDEs and found cursor.com (fork of vscode with AI) to be the 2-3x more productive than copilot or any other AI editors like continue.dev or double.bot or codium. If cursor becomes a great leader, this library is going to be super crucial to get Android development on vscode/cursor. All the power to your hardwork! If I had connects with cursor team, I'll ask them to fund this project.

[AlexandrosAlexiou]

The build folder is excluded when searching for sources, usually generated sources go to target/generated-sources.
To allow this we need to allow the build/generated folder to be searched for sources.

Not sure if there is a convension on where to locate generated sources, there should be one.

[josuf107]

Unfortunately the code generation for the protobuf gradle plugin (and other such tools) outputs by default to $buildDir/generated/.... But target also looks to be excluded.

I notice this issue has come up multiple times e. g. #464, #594.

Using .gitignore doesn't solve the issue because not everyone uses git and because it is common to git ignore generated source files, even though you would expect an IDE to be aware of them.

I would vote to remove build and target from the hardcoded list of directories to exclude. Most likely one would expect a kotlin source file in either to work with go-to-definition and friends. If performance is the concern, we could add a config flag, but I doubt anyone would ever bother flipping it.

I can submit a PR.

[AlexandrosAlexiou]

I have submitted a PR to add the target/generated-sources when indexing here, let's see what the maintainer thinks of this PR and then you can open yours on top of these changes.

[josuf107]

Oh I didn't see your PR until just now. I also have a PR #637, but it takes a different approach, adding a configuration option for specifying exclusions. The only thing that bugs me about it is that it checks the patterns per directory piece, rather than relative to the workspace root, which might lead to unexpected results. That's fixable, and maybe I'll get to it. Otherwise I still think gitignore is not the right way to go, since it is a different concept from ide-ignore and they will often differ when it comes to generated source files.

[AlexandrosAlexiou]

Oh I didn't see your PR until just now. I also have a PR #637, but it takes a different approach, adding a configuration option for specifying exclusions. The only thing that bugs me about it is that it checks the patterns per directory piece, rather than relative to the workspace root, which might lead to unexpected results. That's fixable, and maybe I'll get to it. Otherwise I still think gitignore is not the right way to go, since it is a different concept from ide-ignore and they will often differ when it comes to generated source files.

Good to know, thanks, let's wait for maintainer feedback.