Tagging onto the above, I would really, really lov...
# ksp
z
Tagging onto the above, I would really, really love something that makes it easier to set up KSP processors in Gradle config for users. Compared to the old
ksp("coordinates-go-here")
solution, the new way of several declarations, per source set, all stringly typed is very tedious and error-prone 😞 I think it would be a safe assumption, at least by default, that I want to apply KSP to all platforms I have set up? I assume there are stats about the most used processors, it would be great to take a look at what their normal setup code looks like and if something could be done to simplify this for the happy path at least.
âž• 4
e
I thought this would be the solution, but it stalled a few years ago
yes black 5
💯 1
z
@Ting-Yuan Huang What happened with these efforts?
t
+ @Hakan Mehmed. There was an attempt to specify processors in kotlin DSL a few years ago, but that didn't work out for groovy so it didn't get merged.
m
@Ting-Yuan Huang looks like all the functionality was gated under a feature flag ? (
ksp.multiplatform.enabled=true
) Would you consider merging this as a first step for the
.gradle.kts
users (also to get more feedback about the API)? And then groovy can be added later on?
âž• 2