I seem to remember a custom gradle hook for IDEs to run for code generation. My situation is using ...

# gradle

[yschimke]

I seem to remember a custom gradle hook for IDEs to run for code generation. My situation is using grpc, if a branch has changes to the proto definitions, I need the grpc generation to run whenever I switch branches. Obviously it works when you run, but would be nice not to stare at red lines until the first build.

[Vampire]

Not aware what you could mean.
But you could define a lifecycle task called generate in your build that depends on all code generation tasks and then configure your IDE to run that task before or after sync.

You can also configure this automatic task-running using the idea-ext plugin if your IDE is IntelliJ.

[Vampire]

Actually, if the code generation tasks are properly registered as `srcDir`s, the IDE sync could maybe trigger the getting of the source files and thus cause the generating tasks to be executed. But I'm not aware that either IDE is doing that currently.

[Trevor Stone]

// This triggers code-gen immediate on gradle sync
afterEvaluate {
    tasks
        .maybeCreate("prepareKotlinIdeaImport")
        .dependsOn(tasks.getByPath(":${project.name}:kspKotlin"))
}

This is what I use for jvm KSP

[ephemient]

actually supported: https://www.jetbrains.com/help/idea/jetgradle-tool-window.html#gradle_context_menu:~:text=Execute%20before%20Sync%2C%20Execute%20after%20Sync or https://github.com/JetBrains/gradle-idea-ext-plugin/wiki/#gradle-tasks-triggers-settings

[yschimke]

Thanks @Trevor Stone, that's the one. Think I saw this tweet https://twitter.com/Sellmair/status/1619308362881187840?t=ZmXcptNjl5b2OfLCNEePmg&s=19

[Trevor Stone]

Yep, that's where I learned about it. I couldn't find the initial slack reference for it. Glad you found the tweet