KSP support for retrofit-response-type-keeper

[nedveed]

KSP support for retrofit-response-type-keeper

[JakeWharton]

I'm personally not interested in maintaining a KSP version right now. Perhaps once it moves into the Kotlin repo and KSP2 is stable we can reconsider.

[JakeWharton]

The logic is really simple. Someone can maintain a KSP version outside the Retrofit repo until KSP is stable enough to move it in.

[nedveed]

I see. I wasn't aware that KSP is not stable enough due to Google recommendation to migrate.

Kapt is now in maintenance mode, and we recommend migrating from kapt to KSP wherever possible. In most cases, this migration only requires changes to your project's build configuration.
https://developer.android.com/build/migrate-to-ksp

In my case, in project with 15 endpoints, kapt task has ~7s while full release build has 4m30s, and it doesn't affect dev builds at all due to kaptRelease, so maybe it's not that big deal as it isn't like generating some big Dagger graph and it's reasonable to wait for KSP2.

[JakeWharton]

Separating your network layer into its on module will allow reducing that time to effectively 0, since it will always reuse the cached output rather than running on every change.